Clearly a new OpenSSH feature to keep an eye on. This should improved security of the server by default. That said, it needs to be a bit more in the wild before knowing how to best tune it.
This is indeed surprising behavior and specific to Windows. If you wonder why TCP connect is slow and you got IPv6 support active this might be why.
Interesting, it confirms garbage collectors can be the source of unrecoverable performance degradation in request based systems.
Of course it sounds complicated to break Google up... but that's not the point. It's about avoiding its monopolistic position, the fact that it's complicated is just another symptom.
Or why anticipating too much is merely a gamble. You can be lucky, but how often will you be? Also I agree that in such cases the performance will be impacted longer term leading to a death by thousands of paper cuts.
Retries are becoming common place to deal with transient errors. That said, they can be a problem with recovery of longer failures due to amplification. There are options on the table to solve this though.
Interesting take, those bugs are more convenient to exploit. Logic bugs are too specific to easily exploit at scale.
Need to duplicate data in Postgres? Several options are on the table.
Looks like an interesting tool for creating anonymized pre-production environments.
Compile time reflection in C++ will indeed be a big deal.
Funny short video, I guess it has also some tutorial value to know what you can do with Blender? (and no, you can't break the fourth wall with it)
Here is an interesting use of Pydantic to properly model inputs.
Yes, please let's increase the market share of non-Chromium based browsers.
Luckily this kind of very low level vulnerabilities are not too common and difficult to exploit. But when they get exploited all things break loose and you can't trust your hardware anymore.
Looks like a neat extension which can come in handy.
Interesting dive into some of the performance improvements introduced into recent CPython releases.
Surprisingly, I bumped into this article as I'm wrapping up reading the Team Topologies book. This highlight fairly well some of the concerns I have with it and where it shines. I think it's right to turn to the principles it's built on rather than use the model it proposes as a blueprint.
It's bloody hard to build a strategy. This article is full of good wisdom to make one. This won't make it really easier, but at least you won't start in the wrong direction and will be able to know if what you produce is any good.
I'm not sure the incentives are right... it's better to clean up as you go. Still some places would benefit from such an event from time to time and even if you clean up as you go missed opportunities happen.
Someone was about to get revenge, this gives an interesting exploration.