Very cool reverse engineering of the schematics of the infamous Pong game. It had no software and no CPU either. Quite a feat.

A bit on the sarcastic side but there's definitely some truth to it. This definitely goes against the YAGNI principle.

Good advices on using tags properly for versioning.

Interesting opinion. Indeed, as the browsers are packing more features they can deal with more frontend complexity themselves. This is an opportunity to reduce the amount of code in the frontend code at least for some use cases.

Interesting forensic of a supply chain attack targetting crates.io. Especially fascinating to me is how it then tries to target CI build environments as preparation for larger attacks.

Interesting balanced view about Rust. Looks like it highlights strengths and weaknesses properly.

Interesting (although unsurprising) study (I advise looking at the actual paper) about the links between social media and well being. Of course it has a couple of weaknesses, we need more such studies to grow the numbers and reduce the biases.

VLC is really going everywhere. Glad to see it in this new venue.

Indeed, we loath wires... but going wireless has its own set of issues. It never completely breaks but it can easily degrade for no apparent reason which could be anywhere in the stack.

I like it when type systems can express this kind of constraints. It clearly allows to catch mistakes early in the development cycle.

I definitely agree with this. Managing complexity is our trade.

The tone of the article isn't exactly to my liking, sounds "too good to be true" at times ignoring important details driving the choices (despite some warnings early on). Still, depending on the amount of data stored in your database, SQLite looks increasingly viable on the server, replication even coming down the road.

Looks like a very interesting toolkit for low level network related or security related operations.

This is indeed a nice set of tasks to evaluate a frontend tech or your mastery of it. Potentially usable in interviews?

There is indeed a trade-off approach available nowadays between "backend computes the whole page" and "frontend computes it all in JS". This sounds like an interesting patch depending on the project context.

It was only a matter of time until this kind of things would be doable through webassembly. I'm wondering about the size of the payloads the browser needs to download though.

This is in part a rant but lots of points in there are very valid. This is in part why I don't find Go a very compelling option so far. Modern tooling indeed, nice runtime in some areas but leaves way too much of the complexity in imperative code.

Behind the hype... a speculative bubble completely out of touch with reality.

Excellent news, hoping to see more such bogus patents cancelled. Also, one can hope, that patent offices would start becoming less sloppy...

Looks like it's still in the very early days but the overall approach looks interesting.