3 ms·

I was a Java developer, and when Sun was acquired by Oracle, I knew it's time to move on. Now I'm coding Ruby, and whenever I look back, I see Oracle raping Jav

by spajus 14y ago

I was a Java developer, and when Sun was acquired by Oracle, I knew it's time to move on. Now I'm coding Ruby, and whenever I look back, I see Oracle raping Java - suing the good guys, adding malware to Java installers, increasingly introducing new security holes. It's such a sad sight...

__alexs 14y ago
Raping? Is that a technical term?
martinced 14y ago
To be honest a lot of the major security bugs were actually inherited by Oracle from Sun when they bought Java. In 2011 we had two major Denial of Service working on any Java webapp server that were present since more than ten years in Java (one of them was a known-but-never-fixed bug and the other was unknown-but-already-existing). The Java applet SNAFU is totally Sun's fault and the wasted time and energy spent making these applets work (and hence making Java plugins for the various browsers) should have been spent by everyone for most interesting purposes. Regarding the "time to move on", I hardly think so: Java is still increasingly popular and it's very hard to find a big company not using Java anywhere in its stack. And you mentioning Ruby in response to security holes is particularly ironic seen that lately Ruby hasn't exactly been proved rock-solid from a security standpoint ; )
- krrrh 14y ago
  The big "ruby" vulnerabilities that came up recently were issues in rails. I don't think that there's much irony here since the response from the rails core team was fast and professional, as was action taken by the community to patch existing web apps. Oracle sat on known vulnerabilities and didn't scramble out a fix until the department of homeland security got involved. Obviously we're comparing applets and oranges here, but Oracle deserves a heap of criticism over how it's handling these issues, and it really brings the future of their Java codebase into question.
goggles99 14y ago
adding malware to Java installers Actually, the ask.com Toolbar has always been part of the installer. increasingly introducing new security holes FYI One of these two definitely is pre-Oracle.

by spajus 14y ago

__alexs 14y ago

Raping? Is that a technical term?

martinced 14y ago

To be honest a lot of the major security bugs were actually inherited by Oracle from Sun when they bought Java. In 2011 we had two major Denial of Service working on any Java webapp server that were present since more than ten years in Java (one of them was a known-but-never-fixed bug and the other was unknown-but-already-existing). The Java applet SNAFU is totally Sun's fault and the wasted time and energy spent making these applets work (and hence making Java plugins for the various browsers) should have been spent by everyone for most interesting purposes. Regarding the "time to move on", I hardly think so: Java is still increasingly popular and it's very hard to find a big company not using Java anywhere in its stack. And you mentioning Ruby in response to security holes is particularly ironic seen that lately Ruby hasn't exactly been proved rock-solid from a security standpoint ; )

krrrh 14y ago
The big "ruby" vulnerabilities that came up recently were issues in rails. I don't think that there's much irony here since the response from the rails core team was fast and professional, as was action taken by the community to patch existing web apps. Oracle sat on known vulnerabilities and didn't scramble out a fix until the department of homeland security got involved. Obviously we're comparing applets and oranges here, but Oracle deserves a heap of criticism over how it's handling these issues, and it really brings the future of their Java codebase into question.

goggles99 14y ago

adding malware to Java installers Actually, the ask.com Toolbar has always been part of the installer. increasingly introducing new security holes FYI One of these two definitely is pre-Oracle.