monocasa

Way more testable, the bulk can be shared between async and blocking IO, it's a lot easier to completely ban unsafe in your dependencies (excepting std and core), etc.

Six hardware threads, so the thread per subsystem model didn't really work. Instead you got the best results from a DAG of tasks submitted to a job stealing scheduler running on most of the CPU resources. But beside that, no little DSPs that you had to separate work out onto other than the GPU.

And it had the first consumer GPU to incorporate unified shaders (so vertex and pixel shaders ran on the same cores, dynamically scheduled to improve utilization).

This was always going to be a bunch of politiking at this point to get some party to switch sides by giving them a ministership that the size of their party wouldn't normally justify.

Also, Chan14 is really silly to say 60 MKs, given that you need 61 and it's so far out from everyone else's data. It's as big of a number as they can say without having too much egg on their face later.

I bet there's either something the poster isn't telling us, or CBP made a bad call.

It was heartbreaking.

That feels like the ~2010 era of people saying that functions should be as small as possible. That lead me to reviewing a lot of code where every function was one or two lines and you couldn't actually see what was going on anymore through the layers of unneeded abstraction.

I want to give chrome the benefit of the doubt, but that seems really goofy.

I would think they're probably even more meaningful in an agentic world.

Shitty generals can't review meaningfully review the work of their troops.

On top of that all, I just enjoy programming itself. It's less and less of the meat of a software job over time, but I was coding before I got paid for it, and I'll probably keep coding well after I can get paid for it.