Skip to content
Hallway
0:00 / 0:00

#java#briangoetz#jdk12

Java Futures: 2019 Edition by Brian Goetz

Jfokus

12K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Brian Goetz, Java Language Architect
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Intermediate. Assumes working knowledge.

14K views7 years ago1 recommendation

Programming languagesJava and the JVMLanguage design and type systems

Brian Goetz discusses the evolution of Java, its new rapid release cycle, and upcoming language features like value types.

Since last year, we've seen two more major versions of the JDK! What's changed in the last year, and what's coming down the road? Join Java Language Architect Brian Goetz in a whirlwind tour of just some of the features coming to Java next. Brian Goetz Oracle

Why it's here

1 person recommends this

What people say. Recommended for its explanation of Java's modern release cycle and the philosophy behind language feature prioritization.

Moments people linked to

u/BoyRobot777in r/programming • Recommends

On “JDK 14 : The new features in Java 14”

If its general curiousity instead of just complaining, then here: Brian Goetz points out that their release cycle wasn't healthy, and most of the time little features got lost under big ones. This is why var was delayed - it just never cut the priority and got crowded out by big ones.
14View on Reddit

u/BoyRobot777in r/programming • Recommends

On “Java 12 Released”

Brian Goetz points out that their release cycle wasn't healthy, and most of the time little features got lost under big ones. Thus, new release cycle has allowed them to balance this out. This is why var was delayed - it just never cut the priority and got crowded out by big ones.
12View on Reddit

u/BoyRobot777in r/programming • Recommends

On “JDK 12: First Release Candidate”

To clarify some misunderstandings I see in the comments, I just tl;dr Java Futures: 2019 Edition by Brian Goetz. Their general mantra is "First, do no harm". And they believe that a language can become "full", thus they really pick what feature they want to add. Regarding little features, Brian Goetz points out that their release cycle wasn't healthy, and most of the time little features got lost under big ones. Thus, new release cycle has allowed them to balance this out. This is why var was delayed - it just never cut the priority and got crowded out by big ones. The compiler cannot infer type in these situations: \- Intersection types; \- Capture types; \-…
3View on Reddit

u/jschmein r/Clojure • Mentions

On “Clojure Futures with Ghadi Shayban”

It is a nod to Java Futures, a talk by the Java language architect Brian Goetz in the same theme but for Java.
3View on Reddit

u/BoyRobot777in r/programming • Mentions

On “Bryan Cantril on Software values (and why Go is an autocracy and that is ok) [Audio]”

Not in Java 11, because Java 11 is out already. They've been working on value types for several years now, and this year, one of Java architects - Brian Goetz, said they will start delivering them in upcoming year. Source
2View on Reddit

u/BoyRobot777in r/programming • Mentions

On “What Java has learned from functional languages”

>Simple languages like Go being successful have nothing to do with them being good languages, it's that they're easy to understand and adopt by newcomers On that we both agree. >If you can understand what's going on, you will want to switch to languages with more complex features such as generics. Why? If languages like Go and Java can solve problems more straightforward than for example something like Scala. Where yes, code is more dense, you can do more cool stuff with it, however, you have less people who can understand that and a higher learning curve. >you will want to switch to languages You base that assumption on your own experience. However, what I have observed is that majorit…
2View on Reddit