Interesting insights from optimisations done on the Quake engine almost thirty years ago.

We take font rendering for granted but this is more complex than one might think.

This is indeed an excellent technical documentation wiki for the Linux ecosystem.

Quite some good tips in there. If you want to do deep work you need to arrange your organisation for it. Using asynchronous communication more is also key in my opinion.

A bit buzzword oriented, still I think it's true that most of those principles make sense.

Indeed, don't assume they misunderstood the sci-fi and fantasy they read and you know. Clearly they just got different opinions about it because their incentives and world views are different from your.

Automated DMCA take downs have been a problem for decades now... They still bring real damage, here is an example.

There's really a problem with journalism at this point. How come when covering the tech moguls they keep leaving out important context and taking their fables at face value?

I guess when you unleash agents unsupervised their ethos tend to converge on the self-entitled asshole contributors? This raise real questions, this piece explains the situation quite well.

This is a very important initiative. For a healthy web platform we need good interoperability between the engines. I'm glad they're doing it again.

Oh this is bad! The amount of data exfiltrated by those malicious extensions. Data brokers will do anything they can to have something to resell. This is also a security and corporate espionage hazard.

It's nice to still see some activity around IRC.

Wondering if blurs can really be reverted? There's some noise introduced but otherwise you can pretty much reconstruct the original.

No, modularity doesn't imply micro services... You don't need a process and network barrier between your modules. This long post does a good job going through the various architecture options we have.

Clearly early days... Could that become a good place to land for people fleeing off Discord?

Everyone makes mistakes, what matters is how you handle them.

There are lessons and inspirations to find in how the Vulkan API is managed. The extension system can be unwieldy, but with the right approach it can help consolidate as well.

Interesting essay looking at how systems evolve their schemas over time. We're generally ill-equipped to deal with it and this presents options and ideas to that effect. Of course, the more precise you want to be the more complexity you'll have to deal with.

This is definitely a cool hack. Now I feel like doing something like this to every clock I encounter.

I used to do that, fell into the "taking notes on the computer". And clearly it's not the same, I'm thinking going back to paper notebooks soon.