Sure they're pulling some effort on the way their hardware is produced and cheap. But don't be fooled by the grand claims, this can't be carbon neutral.

Lots of possibilities in the JVM to monkey-patch some behavior. Most of them are a bit involved though.

Everything you wanted to know about SQL joins, and more.

Keep the downsides in mind. Rust has an ecological niche, but it's not that big.

Nice to see this effort keeps bearing fruits. This is a very needed engine to avoid a monoculture.

This is definitely a big deal for the Java type system and its ergonomics.

Unsurprisingly after people massively converged to two main closed source engines for their games, they start to be massively screwed over. Maybe it's time for them to finally turn to Free Software alternatives?

Interesting free font. Made for aeronautics, but brings interesting properties which might be useful in other contexts as well. Created around Toulouse and my old University too!

Interesting trick indeed. I'll try this when I get the chance. Clearly this avoids the underwhelming atmosphere closing after most Q&A session.

This is unclear on the technicalities (is it even possible to just claim it like this? is CC0 required? etc.). Still this is a bold move, hats off to this renowned author.

A bit of a rambling, there's something interesting in it though. Splitting small functions early will do more harm than good if they're not reused. Don't assume they automatically make things easier to read.

OK, this is a very bleak view... maybe a bit over the top I'm unsure. There seems to be some truth to it though.

This is a sound advice. In other words, don't commit too early, only when you got enough information. Of course monitor to make sure you don't miss said information.

Lays out the ethical problems with the current trend of AI system very well. They're definitely not neutral tools and currently suffer from major issues.

Good reasoning, multi-page applications should be the default choice for web frontends architecture. The single page applications come at a cost.

A good reminder that depending what happens in the kernel, the I/O time you were expecting might turn out to be purely CPU time.

Looks like the morbid fascination for microservices is fading. This is very welcome. This piece is a good criticism of this particular fad and gives an interesting theory of why it came to be.

Interesting, "state of the union" regarding local-first we frontend. Lots of pointers towards other resources too.

Good process for fixing bug. Definitely similar to how I approach it as well.

Interesting caching strategy. Looks somewhat simple to put in place as well.