wk_end

Canada has a free press, and many of its largest media outlets (the Sun, the National Post, the Globe, etc.) are strongly right-leaning and had no problems tarring Trudeau's Liberals night and day when he was in power. This is a problem you've invented, not the actual issue here.

100%. Although large handwritten software code bases are often indecipherable to the average human being (actually, almost always indecipherable to the average human being, but often indecipherable even to skilled software engineers too); sometimes due to inherent complexities, sometimes due to Enterprise-isms.

That's the way the world's been since the integrated circuit was first developed, for better or worse.

All OP is asking for is the ability to declare variables at first use instead of at the top of a function. You don't need closures or anything that'd inhibit C compatibility for this - C itself has supported this since C99. It's fairly simple if you're willing to give up single-pass compilation, which (I think?) FPC already has.

You're underestimating how wrong this is going to be on average. This is going to be nonsense like half the time. It's not comparable to Google Translate, it's more comparable to Babel Fish circa 1997.

As a native English speaker, I interpret it as “you the reader”. Or maybe I should say, I don’t intuit any material difference between “you the reader” and “any given reader” or “one”. I think your original comment is a good critique of the headline.

No it doesn't; that's a common misconception.

Raycasting (in gaming, some graphics folks just use it as another term for raytracing) means to fire a ray for each column of the screen, identify where it collides with a wall, and use that to determine what to render for that column - it's basically per-column raytracing.

DOOM's engine instead uses a BSP tree so that, from any position, you can determine which walls are on-screen instantly just by walking the tree - the nearer walls appear earlier in the traversal than farther walls. It's still column-based (it tracks whether each column has been drawn and won't draw further walls behind an already drawn column, and stops drawing once all columns are filled), but there's no rays cast.

I'm not totally sure what you're trying to say. Even back in the days of "software rendering" - or on those embedded systems that you're describing - you still had a piece of graphics hardware that converted the frame buffer into whatever got spit out to the monitor, so I don't think this is meaningful, really.

What's meant by software rendering is really software rasterization - the process of taking the triangles, textures, etc. of the scene and turning those into the pixels that eventually make their way to the screen. You can still do that in software on the CPU today without touching the GPU, even the integrated one. At that point you hand it off to the hardware to make its way to the screen, sure, but it's only an implementation detail that makes that different from handing 0xA0000000 over to the VGA card. The interesting part of the process, and the results, are functionally the same.

That probably had more to do with decompression than sound mixing though, right?

"The arc of the moral universe is long but it reverts to the mean" is somehow less inspiring.

Even if they don't own the business, there's still the risk of the profit motive interfering with proper care - the business owners are going to put as much pressure as they can, one way or another, in subtle or not-so-subtle ways, on their dentists to push for expensive treatments. Bonuses, performance reviews, off-hand comments, and so on.