Looks like an interesting tool to have in the box for 2D effects on the web.

This is a good initiative. It makes no sense for Oracle to still cling onto JavaScript has a trademark.

An interesting endeavor to create you own OS using another language than one of the usual ones.

Need to illustrate how much the current AI arm race is an ecological and social problem? Here is a very pathological case. This is what you get when you let the tycoons behind this completely unchecked.

Wish to use SQLite in production? You better have a good backup strategy. This article explains the main available options.

Shell scripts deserve to be well designed like this indeed.

Interesting proposal for a superset of C++ bringing a safe subset. Could it be a way to improve C++ use for the coming decade?

Nice tricks to help the team jell. I should try this more.

A good list to design HTML forms. The bar is indeed high and there's value in simplicity.

Or why going through an event loop might be more work initially but will make some things easier longer term. Nice way to frame how threads are bringing some opaque state.

Nice to see such a project be funded. Let's see how far this will go.

This is bad. There was no way to know the book was AI generated and clearly it contained errors and lies.

This is clearly not a great outcome. The browser monoculture probably doesn't help.

It's good to see servo getting closer to being usable in a browser. Makes me dream of Falkon or Konqueror being resurrected with Servo as the engine.

A couple of flaws in this article I think. For instance, the benchmark part looks fishy to me. Also it's a bit opinionated and goes too far in advocating exceptions at the expense of error values.
Still, I think it shows quite well that we can't do without exceptions at all, even in the case of error values being available. In my opinion, we're still learning how both can be cleverly used in code base.

He is spot on again. The scope is what will allow to create flexibility in a fixed price project. This is what leads to the necessity to work incrementally.

A bit too much of a rant for my taste (even though I agree with the GitHub flaws). That said it illustrates nicely a use of git range-diff which is often overlooked.

Good reminder that packing your data is generally the right move when squeezing for performances.

Interesting exploration of the NT design compared to Unix. There was less legacy to carry around which explains some of the choices which could be made. In practice similarities abound.

Looks like there is still some work required on QUIC. There is a path forward though.