The author has no clue how spending works in cloud environments nor why it's so complicated to calculate. This is a pretty uniformed article.
naonintendois
70k is likely way underpaid for dealing with COBOL. I've heard of people making 200k for being on-call
I-4 was much easier to drive for me than I-95 in Miami. I have never seen worse drivers.
You can have a memory leak when items are still in scope in some loop or when you have a reference count cycle. The latter happens with the Rc/Arc types in rust.
An example for the former can be a web server that keeps track of every request it's ever received in memory. You will eventually run out of memory. But you did not violate any memory rules (dangling pointer, etc.). Memory leaks can be caused by design issues.
You don't need unsafe. Just keep pushing to a vec and never remove anything. Memory leaks are more than lost memory allocations. You can even have them with rc/arc cycles
Rust doesn't prevent memory leaks. You can do that in every language
My only issue with nix is the documentation is terrible.
VRR is variable refresh rate. Not sure about the others
I organized and threw away cables a few times. Every time a week or two later I'd find the things the power cables attached to and now have no replacement because they were unique to the device.
People become nicer on the east coast of Florida as you go away from Miami.
Wow I almost fell for this. Sounds so believable in today's atmosphere.
Gaming is catching up. Valve has done a tremendous job getting games supported with Proton on SteamOS