Indeed, the Fediverse needs to be better known. Any small actions towards this goal helps.
Nice primer on the impact of too many branches in your code on the CPU. This is sometimes a good way to boost performance when you're mindful about that.
Of course I agree with this piece. You need enough culture in your field to know about a breadth of topics. It will definitely help pick up the next one you don't know about yet or help you build parallels for the tougher problems you encounter.
Looks like a neat tool to have available to remap keys.
Looks like the monopolists are vexed and are looking for arguments to discredit the competition... of all the arguments, this one is likely the most ridiculous seeing their own behavior.
I mostly agree with this piece. There's lots of room for optimization still so we might see a temporary drop in the energy consumption of those systems. That said, longer term energy consumption is indeed the main leverage to improve performance of those systems. It can only get us so far, so new techniques will be needed. Hence why my position is that we'll come back to symbolic approaches at some point, there's a clear challenge at interfacing both worlds.
Excellent satire, it summaries the situation quite well.
Maybe at some point the big providers will get the message and their scrapers will finally respect robots.txt? Let's hope so.
I guess this was just a matter of time, the obsession of "just make it bigger" was making most player myopic. Now this obviously collides with geopolitics since this time it's about a Chinese company being ahead.
This is a worthy questioning... We try to reuse, but maybe we do it too much? For sure some ecosystems quickly lead to hundreds of dependencies even for small features.
Finally some sane API to deal with date and time in JavaScript? Maybe, we'll see...
Always be careful with regular expressions indeed. It can badly backfire.
This is good to see funds being raised for those projects. Lets hope they get madly successful.
Nice tricks to say no when people push to get something in a product. 😉
Interesting proposal of structure for technical documentation.
A harsh reminder that getenv is not thread safe...
Nice experiment in minimalism. It's nice to see we can still build tiny systems like that.
Nice musing on how a type system can be a way to tame complexity or at least isolate it explicitly in one place.
Very nice explorations of the different behaviours type systems can have around inference.
This is indeed clear, the centralized web platforms are fragile by default. They are very prone to capture, this is what just happened.