Have a nice day. https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/rust-java.html https://benchmarksgame-team.pages.debian.net/benchmarksgame

Have a nice day. https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/rust-java.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... And that $1.53/hr is per instance. $13,402.80/yr per instance. Now calculate 100 instances. 200. 1,000. Now find a CFO or CTO who wouldn't gladly cut that in half with Go or even more with Rust. At a small enough scale, all technologies work and are affordable. You could run a very small site from your home Comcast network with a Raspberry Pi and bash scripts invoked by CGI. In fact, a lot of sites could do this. But we're talking about software engineering. It's the difference between a steel plate covering a hole in the pavement and a highway bridge. Any ole steel will work just by slapping in down as long as it's a half inch thick. Once you're building bridges, you need to be more and more discriminating in your choices as the size/length increases. Java's advantages in 2005 over C, PHP, Perl, etc. just don't carry the same weight in comparison to alternatives in 2024.