upvote
This ... isn't true? A lot of people perceived the Java plugin as being insecure in the browser, and indeed it was.

The perception of Java as being insecure on the server was only a thing amongst those who hadn't used it much since the Java plugin era.

That's why the Log4j vulnerability was a huge deal.

I like Rust, but this kind of anti-Java-think is super dated and boring.

reply
Java CVEs were mostly holes in Java's own sandbox (e.g. used to run multiple applets from different websites in the same VM) which has been abandoned.
reply
Complete nonsense. Many of the CVEs for Rust are things that just can't happen in the JVM. And many of the Java CVEs require uses of the JDK that few people ever use. You can dynamically load classes in the JVM (or you can turn that off). Its a nice feature that isn't used all that often anymore but when you need it, its very powerful. Lots of security folks made a living reporting CVEs around that. But its also why people are salty about CVEs and Java because they just reported the same security "hole" over and over again. Yes the JVM can load classes dynamically. If you don't need that, turn it off (or sign your jars). But if you do need it, then the CVE is largely irrelevant. That security researchers created this false impression of Java is a big part of why bug bounty programs aren't very popular anymore. Crying wolf gets you put on the ignore list.

PS Its the height of irony that the layer protecting Java webservices IS less secure than the Java webservice itself.

PPS The Java memory model is just superior to Rust's in every way...deal with it.

reply
> PPS The Java memory model is just superior to Rust's in every way...deal with it.

I don't see it. In Safe Rust we can't write a Data Race so we get SC/DRF because we know we don't have a data race. If we write unsafe Rust we do need to be careful not to break the rules and introduce a data race.

In Java we do not get such a promise at all, just the SC/DRF proof, any of our code might race. However, if we do lose Sequential Consistency we still have defined behaviour, we probably no longer understand how our program behaves (if it's not trivial) but we can say e.g. "I didn't write any code to delete the database" and so conclude it doesn't delete the database.

This doesn't seem like a clean win. I can see valuing either proposition more, but "in every way" I don't get that.

reply
>PPS The Java memory model is just superior to Rust's in every way...deal with it.

You forgot the interpreter itself. Good luck.

reply