Teacher: "Photosynthesis makes energy from water, CO2 and light. The mitochondria are the power centers of the cell."

Grade-schooler: "How do they work?"

Teacher: "Um. Um..."

Modern scientist: "Quantum entanglement and tunneling. We don't really understand any of it."

Then there's stuff like this: https://github.com/hdresearch/ziggit/blob/master/src/cmd_bra...

It's just one giant function. Sometimes big functions are necessary. This one is clearly AI generated and not very readable for a human. This is just from a quick glance.

Edit And then I go their repository and read commits like this https://github.com/hdresearch/ziggit/commit/31adc1da1693e402... which confirms it wasn't even looked over by a human.

The GPUs have become much larger, so 6.8x is believable there, as is the inclusion of a matmul unit boosting AI.

The 2.x numbers are the most realistic, especially because they represent actual workloads.

Mobile devices, unless you get really close to the screen, have matched the retinal density for a while. Most people hold the device at about 8 inches, so 450 dpi is the value to hit.

Edit These measurements assume 20:20 vision, which is the average. Many people exceed that. So you'd need slightly higher values if you're feeling pedantic.

Not the best example. That snippet was in use at SGI for years and actually written by Gary Tarolli. Quake's optimization was mostly done by Michael Abrash.

The original id engines were also famously inflexible. They fit the mold of "developing an engine, not a game" to a T. What you saw them do was all they could do. Look at how much Half-Life needed to add to be viable. idtech3 also only broke out of its niche because Ritual and Infinity Ward heavily modified it and passed it around. There's a good reason the engine-based ecosystem is so prominent now.

Everybody's so worried about getting in on the ground floor of something that they don't even imagine it could be a massive flop.

If you use it like an agent and stick it in a loop and run it until it achieves a specific outcome it's not.

However, unlike PulseAudio, I've encountered few problems with systemd technically. I certainly dislike the scope creep and appreciate there are ideological differences and portability problems, but at least it works.

Personally, I'm anxious to do some bigger rust projects, but I'm usually put off by the lack of decent bindings in my particular target area. It's getting better, and I'm sure with some time the options will fill out more.

It would have been much easier and cost-effective to use wlroots, which has a solid base and has ironed out a lot of problems. On the other hand, Cosmic devs are actively working on it, and I can see it getting better gradually, so you get some indirect manpower for free.

I applaud the choice to not make another core Wayland implementation. We now have Gnome, Plasma, wlroots, weston, and smithay as completely separate entities. Dealing with low-level graphics is an extremely difficult topic, and every implementor encounters the same problems and has to come up with independent solutions. There's so much duplicated effort. I don't think people getting into it realize how deceptively complex and how many edge-cases low-level graphics entails.