This is a good illustration of how flexible and expressive Lua can be. Gives ideas to make DSLs.
C++ too can have its own supply chain disasters with enough effort!
Another post which shows that the right technical job interviews are the ones creating a real conversation. It's the only way to have a chance to figure out what the candidate is made of.
This could be a piece full of nostalgia. There is a bit of nostalgia of course, but it's also a path to use what we got in a more valuable and humane way.
This part of the industry is struggling more and more (or more likely silently taking more risks to hide the struggle). It has no path to sustainability and it starts to show.
Indeed, the memory layout of your structs can matter. Be it Rust or not, but in the case of Rust the use of Option might give the wrong feel about the resulting layout.
More in depth look at the launch white paper and the issues covered in the PR. Not much survives scrutiny... there's nothing special with this model.
A reminder that path based APIs and security don't go well together to manage files.
Interesting piece which gives some perspective on the path which led to async/await. It seems to omit some pieces of the history to me but that's a minor issue. I like how it points that it indeed led to gradual improvements locally for developers writing their functions, but is overall leading to larger issues in the involved ecosystems.
A single CLI tool for any Git forge? This sounds appealing.
Indeed, and it's going to get even crazier at some point. I guess somewhat soon but who knows...
Architecture work is not only technical, you need processes to put the architecture of a project in place. That said, you can make things easier with standards to smooth the path toward the preferred types of architectures in your organisation.
Nice quality of life improvements for the history rewrites. That said, I'm particularly looking forward to the changes in hooks handling, it's always been a pain to deal with in teams, moving them to config should help.
People are manipulating vanity metrics to attract VC money? Who would have expected? This is so unsurprising, I don't even understand why people look at those...
Clearly, any endeavour which has to scale will need some form of bureaucracy to stay afloat. The art is keeping it to a minimal before it starts to be an end in itself.
OK, I find it funny. That said, there's a kernel of truth in this piece: there's clearly a taxonomy of bugs and you better know on what you just stepped.
Indeed, architecture work is not only technical (what is really?). You definitely need to account for the organisation and the process to actually put the architecture in place. It's not just about having pretty pictures.
Pausing a game is not as simple as it sounds. There are many approaches to it.
Finer grained borrowing is still something people need in Rust. Here is a potential solution to get them today.
One of the dark sides of our industry, and this is is accelerating at a worrying pace. Maybe it's time to look at and fix the whole hardware life cycle?