brian
things like oauth, binary websockets, loads of headers, etc all are way worse in curl than others. postman is terrible but there are plenty of other gui/cli options
I find it useful since I'm normally turning it off to prevent it from connecting to something right now (speakers so someone else can connect etc), and I never have to think about turning it back on
mine gives this panel if I turn it off. I imagine that second switch does what you want 
all of their examples are pre ai anyway. it's almost impossible to change a core data model thing without ai too.
all the legacy codebases I've worked in have very much been shaped by the original abstractions they decided on. as much as I wanted to change them, there wasn't really a way to do so because of the scale and backwards compatibility requirements
some things are easier to change than others. it's easy to slop on new features, rewrite them etc. changing core models after you've built a ton on them isn't easy, even with ai. the odds it comes up with the perfect data model aren't great, but for isolated features that doesn't matter since it's easy to throw them away and rewrite
I love btrfs and have a similar partition setup, but I'm not sure if the rest of the setup that'd be required to install into this is going to be good for someone wanting assistance with moving their home directory. in particular likely not being able to use any graphical installers since I don't know any that support installing into subvolumes
depending on how much free space you have on your drive and the size of your home folder, the easiest way would just be to
- boot into some live image with gparted (basically any live image)
- use gparted to resize your root and add a new partition for /home
- copy the whole /home folder contents over to the new partition
- if you want your existing install to work: edit your fstab to mount the new partition as /home. the arch wiki should have good instructions for this, doesn't matter if you aren't using arch
I do think they should have taken an approach similar to prettier and gofmt. very minimal settings and opinionated so all js/go codebases are effectively the same formatting
the trend of serverless means that people are writing a ton more programs that are smallish single endpoint things. not that a ton of people are using java there, but that was a major motivation for c#
steam is one of the few commonly used 32 bit apps left on linux.
I imagine most of it is bc most other things are oss and have been updated/rebuilt already. having to run a 10 year old binary happens way less on linux than it does windows.
a handful of distros have tried to remove 32 but support they've gotten backlash bc they'd lose steam support. linux the kernel won't drop it any time soon, but there's a good chance that if steam drops 32 bit, so will fedora etc
most things should have an alternate implementation, just in the unit tests. imo that's the main justification for most of SOLID.
but also I've noticed that being explicit about your interfaces does produce better thought out code. if you program to an interface and limit your assumptions about implementation, you'll end up with easier to reason about code.
the other chunk is consistency is the most important thing in a large codebase. some of these rules are followed too closely in areas, but if I'm working my way through an unfamiliar area of the code, I can assume that it is structured based on the corporate conventions.
I'm not really an oop guy, but in an oop language I write pretty standard SOLID style code. in rust a lot of idiomatic code does follow SOLID, but the patterns are different. writing traits for everything instead of interfaces isn't any different but is pretty common