I don't believe life has chapters. We live now. The past only exists if rooted on present's memory. I don't think we can choose what to remember, but we sure can decide what to nourish. Good luck, enjoy the journey.
We should not blame "the gov" or "organizations". This kind of crap was coded by someone, maybe more than one person. These are the people to blame. Our profession will never be a truly profession until we (developers) are not held accountable for the crap code that we wrote.
For some (maybe many?), consumption of social media fills a huge void. For those who have lasting friendships, frequent social gatherings, nearby (and united) family, quitting social media can be as easy and feasible as the author suggests.
I am all against standards and engineering boards defining what is right and what is wrong, but at the same time I also favor software developers being held civil and criminal responsibilities for the outcome of their work. It is pretty hard to have the second without the first, so here I am at a crossroads.
Here in Brazil its very common for healthcare workers to have a 12h/36h schedule. They work 12 hours and rest one and a half day, in theory. This kind of schedule was heavily pushed by unions and even coded into law. The end result is that I don't know of a single healthcare worker who doesn't have more than one job. They are working 60 hours/week...
We need to give credit were credit is due. Torvalds deserves it, not because of all the code the he wrote, it was not that much and many others could have done the same, but the process that he developed was (and still is, the key). He managed to get together the hacking community AND the industry. Think about all the work involved in merging features and fixes: gazillions of patches. From this work, git was also born and again the genius in Torvalds knew that his job was done, he paved the way and promoted Junio Hamano to be its maintainer.
Sure, classic CGI is one process per request, but even on php-fpm or apache prefork/mod_php each process will only work for a given maximum number of requests, thus refreshing periodicaly. Also, if any of these workers is killed (say, by the OOM-killer), none of the concurrent requests will be affected. Also, the overhead of parsing is almost zero when you have the opcache extension loaded.
I'm not a huge fan of the language, but the PHP runtime wins me by its simplicity and robustness. I work daily on a codebase that has hundreds of millions of page hits per day and 100k QPS during peak hours running on LAMP with a very few servers. We face challenges like everyone else does, but we never had outages because of the languange/runtime.
The language/runtime is very configurable. Some codebases will set strict_type=1 plus error_reporting(E_ALL) eliminating many instances of these kind of problems / footguns.
And that is also why PHP is so robust: shared nothing. Preforking. Time and memory limits per request. Uncaught errors ends only the current request and so on...
Looks like apple is using nvme as an infinity swap. This helps explain how 8GB feels enough and will probably be cause of future pain when those chips begin to wear out.
Judge de current situation by ethical standards of the present and judge historic ones with the eyes of those days. Eugenics was, once upon a time, seen like "good stuff" all around the globo, not anymore.
Steam was always a high target for hackers and a low target for law enforcement (who cares about your stolen games?). It makes a lot of sense for them to implement every security method conceivable.
It's nice to run a common distro on such tiny resources, but things tend to pile very fast when you add packages because of long (and sometimes unneeded) dependencies chains. That's when more specialized solutions shine (like openwrt or buildroot). Kudos to the author.
Do you remember the old days, when desktop apps (many written in Delphi) connected directly to the SGDB, relying on views and stored procedures? This kind of "server-client" software is still very common inside corporate LANs. Since the browser speaks a very limited set of protocols, projects like postgREST are just a bridge between frontend and storage, thus moving all needed business logic inside into the SGDB. This kind of model is hell. It's history repeating itself all over again.
Why should I? the whole idea is error prone. I have seen, many times, in the wild, excessive data exposure thru REST APIs. Lowering the bar does not help.
I like to think that the universe is discrete, composed of "slots", like a big multidimensional array. If you imagine that the discrete universe has some kind of transition, where the properties of a given slot can be transferred to a neighbor slot, then the speed of light is the upper limit on the rate of change. Why does this upper limit exists? We don't know, maybe we live in a simulation, maybe the universe would no be stable enough without this limit.
There is an issue not being discussed here. The guy is almost homeless. He is probably angry and has nothing left to lose. Now think about all the damage he can do by having his open source project being used by so many people and companies. He can deploy a malware or ransonware and even if he doesn't make a penny, he can create some chaos.
This is the real risk of relying on a fragmented open source ecosystem, especially the NPM platform. Pinning is not enough when every Node project uses so many dependencies coming from so many developers.
Here in Brazil we had DST until last year. DST here was called "Summer Time" and it was a complete cargo cult copy of what is done on the north hemisphere. The whole situation was so complicated that only half of the states on the same timezone (we have 4 TZs) had DST because of their distance from the equator line.
The point is: statistically, having above average IQ can give you some advantage. Maybe 5%, maybe 25%. The same advantage can come from many sources, like: be born on the "right" country, have a certain weight, height, skin color, religious belief, economic background, etc.
Think about the USA. The year and city where you're born/raised can outweigh your IQ when trying to predict income, life expectancy, etc.