3 ms·
No reason? I'd say their ham-handed approach to security and their contentment to sit with their thumbs up their arses, while vulnerabilities whose magnitude c
by Karunamon 14y ago
No reason?
I'd say their ham-handed approach to security and their contentment to sit with their thumbs up their arses, while vulnerabilities whose magnitude compare favorably with the US national debt are being exploited widely is more than enough reason to hate Java.
At least Microsoft has the good sense to issue OOB patches when something serious enough comes up!
The current state of Java means that running the browser plugin paints a huge bullseye on your back. It got bad enough that the freaking department of homeland security recently issued a warning to disable the plugin for your own good.
- sc0rb 14y agoThen stop running it in the browser. Do you have any idea how ubiquitous java is in the enterprise? Everywhere uses java. Have you ever worked on anything that needs to be scalable, extensible and maintainable?
- Karunamon 14y agoEverywhere used Flash, and look at where that's going. Ubiquity is not a valid response to "this sucks, we should start thinking of better ideas". Scalability, maintainability, and extensibility are not unique to Java.
- chc 14y agoNobody's talking about the browser plugin. That just adds noise to the conversation.
- Karunamon 14y ago> Nobody's talking about the browser plugin. If you're talking about Java, you're talking about the browser plugin. It all executes on the same VM. You can't simply declare it off limits given the massive and repeated security issues surrounding it, combined with its ubiquity (especially for countries not ending in "America" - Clientside java is very popular in European banks.)
- chc 14y ago> If you're talking about Java, you're talking about the browser plugin. It all executes on the same VM. I can't see how this makes any more sense than "If you're talking about Visual Studio, you're talking about Mac OS X. It all executes on the same processor." Yes, they both share the same underlying technology, but they are hardly indistiguishable — you can certainly talk about one without addressing the other. You could delete the browser plugin from every computer on the planet and it wouldn't make normal Java apps work any better or worse. The plugin depends on the Java platform, but the Java platform is not in any way dependent on the plugin. > You can't simply declare it off limits given the massive and repeated security issues surrounding it I'm not declaring it "off-limits" — I'm suggesting that it is irrelevant to the discussion here. Yes, there are security issues with it, but since nobody here is saying "I think the Java browser plugin is a boss idea," you're either arguing with nobody or trying to denigrate the JVM as a client and server technology based on the fact that it isn't suitable for embedding in a browser. I can't see any way that the Java plugin is really relevant. Similarly, if I went and wrote a terrible plugin to allow Ruby "applets," bringing up that plugin as a criticism of Ruby in other contexts would not be productive.