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?
When possible it's nice to nest your error types, this allows better investigation when something fails.
Looks like a small syntax adjustment, but that indeed open the door to nice improvements.
The FSF is now weighting in on the Euro-Office vs OnlyOffice situation. You have to respect the spirit of the AGPL and can't take away freedom with extra clauses. Seems to make sense to me.
This looks like an interesting agreement. E2EE messaging anyone? There is more of course, but I'm especially excited regarding this one.
Probably not... This is really taking a long time to be adopted. It's not an incremental thing at all, this doesn't help.
Are we surprised it's mostly a PR stunt? Not at all. Of course, I agree a lot with the conclusion: we can't trust any claim from those companies. They try to present themselves as labs but mostly try to disguise marketing as research...
Interesting piece, shows quite well how new technologies get in the home and then slowly expand. In the case of the Internet, it was indeed literally in a corner of the home before slowly being woven in our lives.
Stop looking at the shiny toy, remember the ethics behind them...
It's first a great marketing stunt. The model is likely not the secret sauce though.
This is indeed a nice pattern for dependency injection in C++ for global functions.
Those have no name... but you'll encounter them regularly indeed.
This bears repeating of course. I still wish our industry would run less on hype. It's not specific to Rust of course.
Of course I wish more meetings would follow this pattern... or not happen at all, sending me a proper document instead.
There's a whole swat of solutions for very lean services. You can go a long way reducing complexity as much as possible. Less infrastructure bills are definitely welcome.
Or why I tend to favor desktop applications (made by KDE as much as possible) rather than web applications whenever possible. It's just more pleasant to have things which look and feel homogeneous.
Looks like someone is actually paying attention to what's going on.
A good primer about design documents. What's nice about this one is the focus on the process rather than the form of the document. Indeed what matters is the shared understanding and making sure the right decision is made.
Can crates.io make things easier to secure? I do think so. But this post is right that we shouldn't forget the social aspect of the whole supply chain security conversation.
Indeed, the current supply chain model of Rust could be better. While we wait for improvements (with no sign of them coming), there are ways to try to avoid some of the common pitfalls.