These are two sides of the same coin, and both of them miss the point. You should be dealing with scale, and you should use a language that allows you to concisely describe how to compute large amounts of data easily. The best part is that once you start writing APL, you'll feel like a wizard.
You're forgetting the part where they had an option to disable this fuckery, and then proceeded to move it twice - exposing containers to everyone by default.
I had to clean up compromised services twice because of it.
The amount of ink that comes with an inkjet printer is tiny. So a new printer comes with 10mL of ink, and the refills are 35mL or more. You quite literally get what you pay for.
The other reason is that inkjet printers need to be used on a regular basis, or the ink can dry out. But manufacturers have handled this by having the printer drip out tiny bits of ink all the time, so it's literally using the ink even when you aren't using it.
For the vast majority of people, a cheap laser printer is the far better option. Unless you want to produce art prints, but at that point you're looking at spending a ton of money anyways.
I get very far by just keeping a set of folders for each piece of equipment in a git repo.
Pictures, etc, and sometimes the PDF manual if I bother.
The difficult part here is being consistent over time - making sure you mark down when you bought things, serial numbers, etc. a proper website/app will force you to do this, but there is flexibility in having whatever convention you like most
Throughout my career, I have used (in no particular order)
Eclipse (as Android Studio)
IntelliJ (as Android Studio)
SublimeText
VS Code
IntelliJ (as IntelliJ)
various CLI editors when sshing into servers (vim, nano, a few others)
Switching your muscle memory takes a long time, which is why you have things like spacemacs, or different keybind presets for almost all of these editors.
There is more value in understanding how to extend and customize your editor than in searching for a new one. Use whatever your workplace provides the best support for, and then customize it from there.
Having worked with data.gov extensively, this may be a huge nothing burger. The number of datasets fluctuates constantly, and ultimately the vast majority of those are just links to specific agencies. If you're lucky, they link the to actual data, but most of the time the link just goes to a landing page for the team that collected the data.
The project stopped running years ago, or I'd pull actual statistics on what was removed or if there's a shared keyword.
But running and syndicating articles based on two screenshots is not particularly useful. At least send in a FOIA request to find out which ones were removed.
Clearly your gender field is a boolean. Which means it can be either true, false, null, or undefined. Except in javascript where for some reason it can sometimes be NaN, but only when you try to compare two people.
That's what binfmt is for