News for hackers. Stuff that matters.
Re:Security of Java takes a dangerous turn for the worse, ex... by jared314 on Wednesday September 11, 2013 @11:19PM (#6371845)
It is alarmist and misleading, but it is also something that will continue to detract a new user's view of the JVM as a platform, like startup time. This is more a PR battle than anything else.
Re:Security of Java takes a dangerous turn for the worse, ex... by jebblue on Wednesday September 11, 2013 @11:47PM (#6371940)
>> It is alarmist and misleading, but it is also something that will continue to detract a new user's view of the JVM as a platform, like startup time.

No, it's just alarmist and mis-leading, the answer is upgrade. That's the answer for Java, Operating Systems (example Windows XP), Smart Phones, it's how software has worked for decades. There's nothing new about it.

Someone got a wild hair and posted a sensationalist title that JavaScript people on HN would like and want to jump on.

Re:Security of Java takes a dangerous turn for the worse, ex... by pekk on Thursday September 12, 2013 @12:02AM (#6371987)
Startup time is a legitimate issue with the JVM...
Re:Security of Java takes a dangerous turn for the worse, ex... by pjmlp on Thursday September 12, 2013 @01:59AM (#6372321)
Which JVM? There are plenty to choose from.
Re:Security of Java takes a dangerous turn for the worse, ex... by SCdF on Thursday September 12, 2013 @04:56PM (#6376898)
So in terms of client-side startup it can become a pain, because if you're starting and stopping a jvm all the time you tend to feel it.

You encounter these problems if:

- People write unix-style tools on the JVM (imagine if ls was a Java program). Thankfully almost no one does this, but...

- When you use tooling for things that involve JVM languages, such as Clojure's lein or Scala's sbt. Starting lein / sbt is annoyingly slow. Using Scalaiform to format scala code takes a noticeable chunk of time because it's booting up a jvm each time. So noticeable that as much as I'd like to have it happen every time I save a file it makes SublimeText way too choppy.

This is less noticable on faster computers (my current work box is a i7 laptop with 12GB and an SSD) but on older computers it's still a real pain. Working with Clojure on a 2009MBP can be an exercise in frustration.

Re:Security of Java takes a dangerous turn for the worse, ex... by pjmlp on Friday September 13, 2013 @01:16AM (#6378798)
You are assuming there is only ONE JVM, which could not be further from the truth.

There are JVMs on the market that compile to native code, and others that cache the JITed code from previous executions. Aonix and Websphere Real Time JVMs are two possible examples.

I really think developers should broaden their horizons. Oracle's JVM is only the reference implementation.

Re:Security of Java takes a dangerous turn for the worse, ex... by sixbrx on Thursday September 12, 2013 @07:11AM (#6373334)
The one you have to use when you don't get to place all of the working code in jeopardy of not working in random places on your own initiative at the place that you work. WHich almost always means Sun's JDK or OpenJDK.
Re:Security of Java takes a dangerous turn for the worse, ex... by pjmlp on Thursday September 12, 2013 @09:14AM (#6373759)
That can mean Oracle, IBM, Aonix, Azul, JamaicaVM, JRockit, HP-UX on my line of business.

So again which one?

Re:Security of Java takes a dangerous turn for the worse, ex... by sixbrx on Thursday September 12, 2013 @02:00PM (#6375731)
I know there are a bunch of JVM's. Just trying to make the point that for most people in most organizations, there's really no choice in the matter, leaving only Oracle's JVM or the OpenJDK - due to the weight of potential compatibility issues, need for retesting, uncertainty about future support/viability, etc. That's a large organization for you, I'm sure it's different at smaller shops and I can envy that.
Re:Security of Java takes a dangerous turn for the worse, ex... by pjmlp on Thursday September 12, 2013 @02:59PM (#6376175)
Fortune 500 consulting, average projects tend to be 3 development sites with offshore component, having around 30 to 100 developers on project.

Typical enterprise stuff.