I'm surprised you are still argueing against the moving goalposts
UFODivebomb
I'd like to see state space coverage instead of line coverage. That, at least, catches silly "100%" cases.
I don't know of a tool that provides this metric. I don't even think such a thing could be made for most languages. still, useful to think about when reviewing code.
Cost is not the immediate issue: time is. The ammo required takes time to manufacture. Russia is not going to wait.
Whether that justifies cluster ammunition no idea. An audit would be enlightening for sure. Unfortunately, none of that results in ammo where it's needed right now.
Some people want to be Trump 's bitch. That's the only explanation haha
Good article but they didn't need the sensationalist title. "often" implies >50% in common discourse. The cited rate is 14.8%. terrible, but not often. Downvoted, unfortunately.
Thanks! Big nix fan myself and very happy to see some Scala derivation help.
Java is improving rapidly. As is the JVM. They are both quality tools that might be the right tools.
I don't program in Java but I do Scala and am familiar with the JVM. The JVM is hard to beat for observability and predictability. Businesses love predictability. Especially enterprise. "500k more? But predictable? Fuck yes." See also: backwards compatibility.
That said the JVM needs to change. Check out the project Valhalla blogs. At the same time the science and engineering of building languages and systems has improved. "New" does not carry the same risk as what the 00s would lead one to believe.
Memory safety is a huge value. I'm sticking to Scala - more my style. Rust is memory safe and native. Which is kinda fucking awesome. So I can see the appeal.
Tl;Dr. Java bad? No.
That's not the title of the article and the article is an opinion piece. Downvoted.