Tempted to do some XSLT? Did you notice it's almost 2025? So yeah, just don't. At least there's a proper alternative if you still need to process that XML input.
More shady practices to try to save themselves. Let's hope it won't work.
It's clear that a split is forming in the C++ community on how to evolve the language. Could it lead to a full fledged divorce?
Looks like there is a new venue to improve garbage collectors performance. This should be interesting down the line.
Another rebuttal of Clean Code. Most of it makes sense if not overdone. There's the usual confusion around the "unit tests" term though, so take that section with a pinch of salt.
Interesting approach to have secure and decentralized naming while keeping it human readable.
The water problem is obviously hard to ignore. This piece does a good job illustrating how large the impact is.
Technology isn't neutral. It's impossible to ignore the ideologies of the moguls funding or leading big tech companies. We can't afford to trust their promises.
Definitely this. Sure we should seek for decentralization, but this is not going to happen or be effective without regulation. Ensuring privacy is a legislative and political problem as much as a technical one.
This is a good point. Idiosyncrasies are not necessarily a bad thing for naming things. Natural languages are fickle friends, you might need to rely to specific metaphors in order to disambiguate.
A long and comprehensive analysis of Bluesky. Also brings interesting critiques about both Bluesky and the Fediverse. Clearly Bluesky as of today is not effectively decentralized and shouldn't be considered as such.
We always think about the energy consumption, but large data centers gobble billion liters of water too. This would need to be improved.
OK, the numbers are indeed impressive. And it's API is fully compatible apparently, looks like a good replacement if you got Pandas code around.
Really nice in depth post. Everything you ever wanted to know about antialiasing but didn't dare asking.
Good advice, no one should be a "React developer". Make sure you learn more fundamental skills.
This can change from organization to organization. This post proposes a career ladder which will work in some contexts. What's clear is that it's all about scope and impact.
Good reminder that models shouldn't be used as a service except maybe for prototyping. This has felt obvious to me since the beginning of this hype cycle... but here we are people are falling in the trap today.
Excellent post showing reasons to be skeptical about Bluesky's future. Despite all their likely sincere claims I don't see how they'll escape enclosure and enshittification when their sketchy VCs will want to see money back.
You're on the fediverse and you want to reach out bluesky users? This might be the right tool for you (unclear if it'll scale yet though). At least if and when Bluesky turns bad, people will know where to reach friends next.
This is what we get for refusing to regulate social media and for not auditing their algorithms. Their owners can game and bias the platforms as they see fit for their own gains. They became massive forces of manipulation in the process.