Well, we’ve a single cable coming over from France that makes up about 3% (I think) of our total electricity supply. So “French Nuclear” should be a bigger entry in that table than coal, solar, hydro or bio. That’s not the only import, either, so it’s not completely impractical for the missing percentages to be imports.
You can only store rational numbers as a ratio of two numbers, and there’s infinitely times more irrational numbers than rational ones - as soon as you took (almost any) root or did (most) trigonometry, then your accurate ratio would count for nothing. Hardcore maths libraries get around this by keeping the “value in progress” as an expression for as long as possible, but working with expressions is exceptionally slow by computer standards - takes quite a long time to keep them in their simplest form whenever you manipulate them.
Yeah, I was pondering this earlier. In exchange for giving up quite a lot of the CPU die, you can have some NPU functionality instead; rather than having to offload everything to the cloud, you can preprocess some of it first, and then offload it.
Speech-to-text and text-to-speech plus general battery efficiency are reasonable use cases for a phone, certainly more so than a laptop and much more so than a desktop. But as you note, those models are going to be small, and RAM and backing storage on phones tends to be slow and limited.
Was also considering that an NPU gives no benefit at all unless code has been written for it; it’s a bastard to write code for something so concurrent, and giving up CPU die for an NPU instead of more cores and cache means that your phone will generally be slower unless it’s largely used for NPU tasks. Plus if you need to offload to the cloud for most useful tasks anyway, it’s just a marketing gimmick that makes your phone less good for most uses.
Assuming you had a pretty decent monitor and graphics output in the 90s, it may have been 800x600, but more likely 640x480, and you’d have been using the standard issue bitmap font with no anti-aliasing, blitted to screen using software rendering. Probably in a single colour, too.
Alas, the problem with that is that it doesn’t scale. On xterm a 4K monitor, I can watch Vim redrawing the screen, paging through logs is painful. Use Kitty for the same, it’s instant, I can flip through tabs and split screens too, and have niceties like anti-aliased fonts and transparency if I want them.
Some people spend a lot of time in the terminal, so I can’t fault them for taking the time to make a nice working environment and sharing that work with others.
Finish the transition from X to Wayland?
Good news is that it’s such a bastard to program efficiently that most games don’t make full use of it and you can get away with a certain amount of approximation in its behaviour for speed. Nice work, Sony.
Compare that with z80 or 6502 based machines, where you need to be beyond cycle perfect in some cases. Need to simulate every rising and falling edge for the CPU and its coprocessors in a SNES if you want to avoid every edge case, for instance.
That’s absurdly high resolution for 1994 - it should be at 320×200, although with the “slightly rectangular” pixels that you get in DOS.
I think some of the magic of Doom gets lost in higher resolutions. The odd badly-aliased pixel gives the impression of glinting light, which it obviously does not have, and some of the mysteries of the enemies is lost, since normally they’d just be a few pixels unless you’re dangerously close to them. Gives the impression that it’s more animated than it is, since it would always be shifting. Modern ports will let you mouselook and things as well, which makes it crazy fast; not that you were exactly slow at turning around, back in the day, but you did need to play it in a more considered way.