Indeed, the story of integrating C and C++ with Rust isn't a simple one right now. It might introduce larger attack surfaces. Some improvements are proposed in this paper.
Everything you always wanted to know but didn't dare asking about memory allocators. OK, maybe not "everything everything" but this gives a very good overview on how they work and the trade-offs they have to make.
Doesn't give the whole picture (memory isn't the only important parameter) but interesting results nonetheless. A few surprises in there, Java and C# do much better than one might assume for instance.
Nice list of patterns leveraging the Python type hints for richer and safer interfaces.
Very thorough overview on how registers are used when you get closer to the hardware. Very good resource to use as reference.
Interesting insights about the minutiae of the CTO role.
Looks like a smart and interesting little tool. I definitely needed something like it more than once.
Indeed, the times when we could pretend one was a superset of the other are long gone.
Updating database schema or interfaces between services should take time if you want to limit the downtime. The extra work involved might mean you should accept a little downtime instead. It probably should be on a case by case basis rather than a blanket policy.
Interesting list. Definitely to keep in mind when developing and deploying a web application.
Interesting take. Will it lead to paying more attention to performance in software? Will it be the rise of the specialized CPUs? Time will tell.
A good counterpoint to the "choose boring tech" which I tend to agree with. Sometimes you need to look into unusual tech and it's fine. Just have to do it rarely and responsibly. The context matters.
Interesting take... Is it really practical? Until which size is it viable? What are we loosing by aggregating? Also makes me wonder about alert fatigue... It clearly raises extra questions.
This trend around critiquing code reviews on the argument of "trust" should be challenged indeed. This is just the wrong way to approach it.
Interesting new tool for easily setting up dev environments. The real added value to previous such tools is it's open source nature and the fact that you can fully control on which infrastructure the environments will be created.
Definitely this. It takes time of course, I don't do it nearly enough... I never regretted it though.
The copyright problem in all this is becoming more and more obvious...
Very early days and still hackish to use but that's definitely big news for the Python ecosystem.
Good explanation of how flame graphs are produced and how to read them. Gives a few tips on what to look for to optimize.
Nice piece, not perfect, good food for thought still. We definitely need more ethics in our craft.