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.

Good arguments around the microservices hype. People advocate for it way more than reasonable, this applies only in rare contexts.

Good explanation of why the complexity of CSS code quickly gets out of control.

A good reminder that it's not all rosy with Python type-hints. There's definitely room for improvements.

This looks like a very interesting tracing tool for debugging and profiling purposes.

That looks like a very interesting tool for larger Python based projects. Definitely need a way to profile memory use in there.

I like this approach to technical interview questions. I do something similar in some cases with a mix of reading and writing.

Interesting to see how a more widespread remote work impact people. Unexpected patterns appear, it's clearly not all for the better though.