JDK 8 Release Notes

Post by aardvark179 » Wed, Mar 19, 2014, 8:47 AM UTC

rossjudson wrote: post #229

spiralpolitik wrote: post #210

I have to admit I thought Java was dead in the water after Java 6, but Java 7 while a fairly quiet release was a decent release and Java 8 actually moves the language forward into a better place. As for the future here's what I would like to see: - Separation of language and libraries. Really the JDK should just ship with just a very small core of classes and everything else should be optional installed via a depende…

Multiple return types: Questionable benefit there. Exceptions are nice when used properly. Option classes handle the rest. Categories: Default methods probably do what you want. Get rid of primitives: Are you nuts? It turns out computers work on primitives. It's good to support them. "Proper" generics: maybe you mean specialization, or maybe you mean reification. It's a choice. Properties: If they irritate you that m…

Post by benjiweber » Wed, Mar 19, 2014, 9:28 AM UTC

hrjet wrote: post #248

dapz wrote: post #222

Earlier quoted context omitted.

Isn't map/flatMap and orElse enough, if only for Optional?

It's not enough for compactly expressing imperative logic. In Scala: resultOption match { case Some(x) => println(x) case None => println("error") } Without pattern match: if (resultOption.isDefined) { println(resultOption.get) } else { println("Error") } The .get is the problem.

  import java.util.Optional;

  public class Scratch {
      public static void main(String... args) {
          Optional foo = Optional.of("foo");
          Optional bar = Optional.empty();

          System.out.println(foo.orElse("Error"));
          System.out.println(bar.orElse("Error"));

          foo.map(Print::print).orElseGet(() -> Print.print("Error"));
          bar.map(Print::print).orElseGet(() -> Print.print("Error"));

          foo.ifPresent(Print::print);

      }

      static class Print {
          public static  T print(T val) {
              System.out.println(val);
              return val;
          }
      }
  }

Post by modersky » Wed, Mar 19, 2014, 10:04 AM UTC

noelwelsh wrote: post #260

modersky wrote: post #251

Earlier quoted context omitted.

I think that's a pretty extreme position. First, it will run a lot slower than the pattern matching alternative: optional match { case Some(x) => whatever(x) case None => fallback } Second, I find the pattern matching code much clearer. Sure, it's also longer, but clarity trumps everything.

map / getOrElse is standard in all the Scala code I've seen. Abstracting over the monad is also a pretty big win that has made some big refactorings painless for me. Pattern matching is really only used by beginners IME.

Post by noelwelsh » Wed, Mar 19, 2014, 10:38 AM UTC

modersky wrote: post #266

noelwelsh wrote: post #260

Earlier quoted context omitted.

map / getOrElse is standard in all the Scala code I've seen. Abstracting over the monad is also a pretty big win that has made some big refactorings painless for me. Pattern matching is really only used by beginners IME.

Well, then maybe the beginners do it right? You have not argued against my two points: It's much slower, and less clear.

Post by coldtea » Wed, Mar 19, 2014, 10:41 AM UTC

puppetmaster3 wrote: post #197

edwinnathaniel wrote: post #140

Earlier quoted context omitted.

JS ecosystems in terms of quality, tooling, and engineering is already bad, can't be worse than that really... PS: No, yet-another-js-library-to-replace-jquery is not considered tooling. No, yet-another-replacement-for-grunt/bower/yeoman is not a good sign of the ecosystems. Java has Maven since 2004.

Maven is horible. Hth