Java 12

Post by hkolk » Tue, Mar 19, 2019, 10:48 PM UTC

ilovecaching wrote: post #71

hota_mazi wrote: post #46

Earlier quoted context omitted.

> it's also lost the niches that brought it into existence Applets, JavaBeans, and CORBA. What a loss. > Besides being owned by Oracle, which is enough of a reason to never use Java ever again, That stopped being an issue years ago. OpenJDK is a thing, you know? > Java on the web is dead, I don't think you have any idea about the hundreds of millions of lines of Java that power the web as you know it today. The rest…

Java on the web is a reference to applets running in the browser. Yes, Oracle, the company that sues people for breathing the same air owning Java is an issue. Maybe I am uninformed, but you haven't made a good case that there's any truth to that.

Post by ilovecaching » Tue, Mar 19, 2019, 10:48 PM UTC

jahrule wrote: post #102

ilovecaching wrote: post #22

I understand why Java has to keep on chugging along, but I feel bad for the people that have to be a part of it. It's like watching people keep coal trains going while people are moving to cars. Why? Besides being owned by Oracle, which is enough of a reason to never use Java ever again, it's also lost the niches that brought it into existence. Java no longer runs everywhere. Java on the web is dead, and you can now…

I think you meant Spring, not Swing, when talking about cloud frameworks. And from this it seems to me you are somehow biased against the java ecosystem without hands-on experience to base your opinions on.

Post by spricket » Tue, Mar 19, 2019, 10:50 PM UTC

abalone wrote: post #95

azhenley wrote: post #6

The most interesting new feature I think is the Shenandoah GC. The summary from [1]: "Add a new garbage collection (GC) algorithm named Shenandoah which reduces GC pause times by doing evacuation work concurrently with the running Java threads. Pause times with Shenandoah are independent of heap size, meaning you will have the same consistent pause times whether your heap is 200 MB or 200 GB." The original algorithm…

How is memory efficiency? Usually faster and/or consistent GC performance comes at the cost of extra memory usage. (This is why I'm excited for ARC / Swift on the server...)

Post by gsu » Tue, Mar 19, 2019, 10:52 PM UTC

azhenley wrote: post #5

connorlwilkes wrote: post #3

The new switch feature looks nice, the way it previously used to work was so unwieldy.

In case someone is curious what it looks like with the new -> form: switch (day) { case MONDAY, FRIDAY, SUNDAY -> System.out.println(6); case TUESDAY -> System.out.println(7); case THURSDAY, SATURDAY -> System.out.println(8); case WEDNESDAY -> System.out.println(9); }

  int numLetters = switch (day) {
      case MONDAY, FRIDAY, SUNDAY -> 6;
      case TUESDAY                -> 7;
      case THURSDAY, SATURDAY     -> 8;
      case WEDNESDAY              -> 9;
  };

Post by coldtea » Tue, Mar 19, 2019, 10:53 PM UTC

ilovecaching wrote: post #89

coldtea wrote: post #67

Earlier quoted context omitted.

> I understand why Java has to keep on chugging along, but I feel bad for the people that have to be a part of it. It's like watching people keep coal trains going while people are moving to cars. Yeah, those poor devs with a rock solid, best of class, platform to write code on, with tons of libraries and tooling. > Java no longer runs everywhere It still runs everywhere where it matters. Nobody really cared if it co…

> Whatever. You have me convinced.