11–20 of 251 posts
Great things come from those unwilling to settle.
But the Kubernetes riff was telling: when using a cloud provider, so much of the system management is provided. When we insist on DIY, we get to DIY.
So maybe settling a bit here and there isn't catastrophic.
Earlier quoted context omitted.
The C++ programmers will just switch to C++ 2.0, aka Rust. It's not a big leap.
Sure we will. Just like we switched to C++ 2.0 aka Java.
How did the C++ committee cause this?
Makes me wonder if I've too strongly tied my career to a specific language. However, right now it's not that I'm specifically a C++ programmer, just that the industry (gamedev) is largely C++. I'm sure in for it if that shifts out from under me before I find stable employment though....
The C++ programmers will just switch to C++ 2.0, aka Rust. It's not a big leap.
What is the context of Bjarne being disgusted? Just years of arguing?
I don't get this part. The language you write something in has little to do with how useful the software is. I've had years writing fulfilling software, and years where I was just spinning my wheels.
I sincerely hope that the author finds joy. Great things come from those unwilling to settle. But the Kubernetes riff was telling: when using a cloud provider, so much of the system management is provided. When we insist on DIY, we get to DIY. So maybe settling a bit here and there isn't catastrophic.
― George Bernard Shaw, Man and Superman
I sincerely hope that the author finds joy. Great things come from those unwilling to settle. But the Kubernetes riff was telling: when using a cloud provider, so much of the system management is provided. When we insist on DIY, we get to DIY. So maybe settling a bit here and there isn't catastrophic.
Way too much for most usecases out there. And if you don't understand it, you can't fix it when it breaks.