Interesting issues around cascading deletes in Postgres and how the indices are managed.
Interesting points. If you're making a platform you can't really figure out what to do next in the same way than when usual product management is possible. There are signals to look for to feed your roadmap though.
It's indeed not urgent to have this language feature in Rust. I'm less convinced about the case put forth regarding function overloading not being necessary though. Feels a bit like post-hoc justification in this case.
There's clearly a major issue in terms of environmental impacts with the AI industrial complex. Yes it's also about electricity consumption but not only. We have at last a comprehensive study on the matter. Without major changes it's just unsustainable and something we can't collectively afford.
The automakers still don't care about privacy apparently...
Kind of an unusual read. But I think the message is powerful. We should definitely favor community over tools controlled by the new robber barons.
Fascinating account of what people must go through for proper film preservation. It's kind of weird that it is still illegal. You'd wish there'd be more recognition for such passion.
This is clearly something which bugs me about the Go ecosystem. It's way too coupled to a single Git provider. The approach to dependency management is neat otherwise but more care should be taken about avoiding this GitHub lock in.
Interesting take and exploration for the reasons which might make Lisp harder to read than other languages.
The slippery slop seems clear... If you start generating a bit you'll be pushed to loose full control in the end. Do you think you can learn this way? Improve? I doubt it.
This is indeed an important pattern to build reliable systems. It's worth exploring in various languages. Here is the Rust perspective.
Aren't we loosing sense of community and our humanity indeed?
Indeed web frameworks are not needed for everything.
You're not paying for a couple more intermediate variables. For sure they make things more readable though.
Interesting new family of side channel attacks. Surprising it lingered for so long before being noticed.
This is indeed a good way to reduce the code generated by templates.
Looks like an interesting tool for black box testing. Seems especially suited for full system tests.
Need to mind the memory layout of your structs to get good performance. Often overlooked but that also includes the padding.
Yes, the preposterous statements from the tech moguls have a use. They allow them to gauge how obedient you are. This is thus a political function and a way to check their power. Maybe it's time we collectively start to say the Emperor has no clothes?
Probably more than you think in this setup. And even more in C++ with the STL having years of smart tricks behind it.