- On startup processing begins at a known address, and you put the bootloader code over there. Hardware engineers can guarantee this for you.

- Every time you execute an assembly instruction, the program counter either explicitly jumps to a new location or else it just increments by 1. Hardware people can also make this happen as easily as implementing an adder.

Don't get me wrong, there are LOTS of layers between the hardware and most "useful" programs any of us will ever write. But all of them are pretty understandable. They're often not very complicated, just tedious.

The entire value of redis IMO is that is ISN'T inside your normal application, but rather some shared storage that all nodes can use to coordinate and that survives deploys, but that provides more ergonomic data structures than SQL databases. Caches are only one type of such shared data, but things like feature flags, circuit breakers and rate limiters are also super common (and super useful).

This once again causes oversimplifies history to a few people and some nebulous "structural forces", and provides an attractive but wrong model of how history developed. In software terms we would call this a "leaky abstraction", and this particular abstraction leaks so much it's barely useful at all.

The world is much too complex to be understood by examining less than at least a few hundred million people. That this is beyond the capability of humans is not the world's problem.

Retirement is inherently a choice to earn less lifetime money and pour that time into family and other things you like doing. Waiting for the next vesting cliff is inherently a choice to earn more money and spend less time on your family.

In reasonably balanced games, it usually turns out the "overpowered" strategy is not all that overpowered and that they have huge downsides when played against people who know how to counter them. In real life, which has no requirement of being balanced, we can recognize that certain strategies ((explicitly legal and often even encouraged!) consistently work really well. Choosing not to use those strategies doesn't make one morally superior, just bad at playing the game of life.

That said, "minimizing your own odds of falling into societal cracks" often still includes caring for others around you. On a small scale, being rich but alone because everyone around you went bankrupt and/or became estranged to you is not much fun. On a bigger scale it's just good governance to make sure everyone has food, safety and entertainment, just to keep the pitchforks away.

When the other side either has information that makes it not a bet, or if they have means to influence the odds, the best outcome for outsiders is to not play at all.

And of course, the entire conceit relies on the idea that more accurate information to the public is always good and always outweighs the negative externalities. But is it really all that important to the public good what the most searched artist is on Google in a certain year? Or if an announcer will say a certain word during the super bowl?

Still though, that is about 10 percentage points higher than before Trump took office. Better not to hand him too many tools to exert leverage with.

Sure, the chance is low. But in the current climate people are nervous and it's best not to risk it. The current government has already embarked on a long-term strategy to bring more of critical software infrastructure back in-country, selling the core identity provider software abroad would go directly against current policy.

It seems to me that there is no way that Trump could overturn this decision via Rutte that Trump couldn't accomplish on his own by just threatening the Netherlands directly.

If only there was an entire class of well-studied languages which don't have any such ambiguity. They'd be perfect for programming LLMs! We could call them "programming languages" perhaps.

I wouldn't use Ruby for high performance computing. But for scripting (where runtime is not critical), web services (where transport latency will usually far outstrip the few milliseconds your handler takes) or shell use (where humans aren't fast enough to issue a new command every millisecond anyway), Ruby is more than fast enough.

Either the 1-2 hours is a drop in the bucket compared to what you spend on it anyway (like a blog you still regularly update), or you don't actively update the project but still care enough about it to spend half an evening every few years, or you should just admit you don't care about it enough anymore to do even that. In the last case just delete the project.

Europe:

America: NOT LIKE THAT!!!

Also the very first line on that page is "The Futhark Programming Language" so if you were still confused after that I think it's on you.

In any case, there are plenty of EU giants (ASML, SAP, Siemens, Alstom, Rheinmetall, etc) that are rather concentrated geographically speaking. EU fairness is more a government agency distribution thing, not for private companies.