> Back in the day hackernews had some fire and resistance
Hackernews is a public forum, and the people here change constantly. "Back in the day" there were mostly posts about LISP and startup equity. It's obviously not the same people here now.
> Too many tech workers decided to rollover for the government
Again, not the same group of people. In the 2000s "tech workers" might have mostly been Californians. Now they're mostly in India. Differing perspectives on government, to be sure.
> lazy engineers build lazy key escrow
Hey you should know this one, because it's something that HAS stayed constant since "back in the day": The engineers have absolutely no say in this whatsoever.
This is extremely disappointing all-around. The World Health Organization was at the forefront of sounding the alarm about COVID-19 early on, and was one of the first to start preparing for the eventuality that it would spread beyond it's origin point. While most people in the US were still saying it wasn't airborne, and downplaying the spread potential and health effects of COVID, the WHO was sounding the alarm on that, too. Ah yes. A little satire does the heart good, you know?
I agree there is only so much an organization can do After the spread, countries themselves have to take action in behalf of the organization's directions and procedures. The U.S. at the time took way too long to act, this was a fact, clearly why some governors were in a tweeting match and arguments over this issue. I do not agree with this direction. Clearly there is alternative motive behind this amongst the multiple other useless withdraws and steps taking at this time.
ReactOS is an amazing achievement, for what it is. Building a house is much easier than building exactly the same house without being able to even peek at the original blueprints, or take input from anyone who has.
To that point I hope that more people study ReactOS and get a sense for the Microsoft/IBM philosophy of doing a desktop operating system (which is completely different from the Linux/Unix way). I hope we someday see new operating system projects that use these learnings.
It's not any more true now than it was then. Windows isn't going anywhere.
The author talks about Windows getting worse, and cites someone's low-tier computer taking 5 minutes to start an Unreal game. Nah, not convincing when my NVMe drive works fine.
The author talks about games running on Linux. I guess the author missed the part where half of the most popular PC games have been consistently unplayable for 6+ years because the company doesn't believe that they can make anti-cheat work.
Ironically, based on that theory, the author says that everyone will "follow the gamers". Yeah, they're currently following the gamers... to where the anti-cheat works.
DevOps failed because management never really understood that it needed to be a dedicated team, and that it shouldn't just be a little vassal state of the ops team, nor is it just "backend devs who know ops" who keep getting pulled away from devops work to do backend work.
IF DevOps had been allowed to thrive, we could have eventually reached the holy grail: A Heroku-like environment that developers can use to run their apps. Instead, we stopped short in the no-mans land of k8s, helm, AWS lock-in, terraform, hashicorp, red hat, azure, not to mention tons of spreadsheets owned by the ops team that developers must beg and plead to get changed.
Hackernews is a public forum, and the people here change constantly. "Back in the day" there were mostly posts about LISP and startup equity. It's obviously not the same people here now.
> Too many tech workers decided to rollover for the government
Again, not the same group of people. In the 2000s "tech workers" might have mostly been Californians. Now they're mostly in India. Differing perspectives on government, to be sure.
> lazy engineers build lazy key escrow
Hey you should know this one, because it's something that HAS stayed constant since "back in the day": The engineers have absolutely no say in this whatsoever.
reply