| ▲ | rvz 8 hours ago | |||||||||||||||||||
All of that configuration and it will always be less efficient than Rust, or even Golang. This is why lots of engineers waste time fiddling with options to tune the JVM and still require hundreds of replicated micro-services to "scale" their backends and losing money on AWS and when they will never admit the issue is the technology they have chosen (Java) and why AWS loves their customers using inefficient and expensive technologies. Even after that, both Go and Rust continue to run rings around the JVM no matter the combination of options. | ||||||||||||||||||||
| ▲ | cleverfoo 7 hours ago | parent | next [-] | |||||||||||||||||||
Sure, for a very narrow definition of _efficiency_. There's plenty to complain in terms of the JVM and Java but performance, as in units of work per dollar spent, is not one of them - JITs just have too many opportunities for optimizing generated code. | ||||||||||||||||||||
| ▲ | deepsun 7 hours ago | parent | prev | next [-] | |||||||||||||||||||
All of that tooling and Rust will always be less efficient than Assembler. | ||||||||||||||||||||
| ||||||||||||||||||||
| ▲ | well_ackshually 6 hours ago | parent | prev | next [-] | |||||||||||||||||||
That's a nice source, from where up your ass did you find it ? Go's GC is absolutely awful and leads to nondeterministic pauses and catastrophic latency spikes, especially when the memory pressure and capacity is high. Throw the go GC against a 256GB heap, see how well it survives. Technologies have strong and weak points. Go's strong points are small, targeted pieces of software and having 66% of a binary basically be if err != nil return err. Rust's strong points are that you get to have the symbol<():soup<_, |_| of { c++ }>> while not saying you're writing c++ and feeling really smug when you say that you only needed to use 5 Arc<Mutex<T>> and rewrote your entire software three times but at least it runs almost as fast as some shitty C that does fgets() in the middle of a hot loop. Java lets you spawn spring boot and instantiate a string through reflection because why not. I promise you, I can write allocation heavy FizzBuzzEnterpriseFactoryFactories in Rust too. | ||||||||||||||||||||
| ▲ | arein3 6 hours ago | parent | prev | next [-] | |||||||||||||||||||
Yeah doubt that Recently I had a python friend use the most balls to the wall python backend, he couldnt beleive java was faster, but the numbers werent lying. We did 1 billion iterations of adding a float, took a few seconds in java. | ||||||||||||||||||||
| ▲ | fHr 7 hours ago | parent | prev [-] | |||||||||||||||||||
I was a diehard java fanboy but using Rust in the last 5 years more and more I have to agree, but sadly huge Java corporate codebases keep my bills paid still, so I have to deal with it. It is what it is. Also agree the pipeline etc. they love all the waste of the compute in their pocket. | ||||||||||||||||||||
| ||||||||||||||||||||