Skip to content
0:00 / 0:00

#java#briangoetz#jvm

Philly ETE 2014 #50 - Java: Past, Present, and Future - Brian Goetz

ChariotSolutions

9.3K subscribers • 10 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Brian Goetz

Intermediate. Assumes working knowledge.

2.3K views11 years ago1 recommendation

Programming languagesHistory and cultureJava and the JVMLanguage design and type systemsHistory of computing

Brian Goetz discusses the history, design philosophy, and future evolution of the Java programming language.

When it was introduced nearly 18 years ago, Java was a combination of radicalism and conservatism; it made a bold gamble that garbage collection and JIT compilation would mature fast enough to be useful for mainstream programs, while eschewing then-trendy features such as operator overloading. Java succeeded beyond Sun’s wildest expectations, and now 10M developers program in Java. But the world hasn’t stayed still; the hardware, the developers, and the problems we want to solve today are not the same as they were 18 years ago. So, how has Java evolved to meet these challenges, and how will it continue to evolve in the future? This talk will look at where Java has been, where it is today, and where it may be going in the future.

Why it's here

1 person recommends this

What people say. Recommended as an interesting and informative talk on Java's evolution and design choices.

u/SimonGrayin r/Clojure • Recommends

On “Brian Goetz' favourite non-Java JVM language”

He also alluded to that fact in this old and quite interesting talk about Java: link to this video I'm paraphrasing here, but at one point he asks the rethorical question "why am I working on making Java more functional when I could just use Clojure?". BTW you should watch the talk. He's a great speaker.

u/pron98in r/haskell • Mentions

On “From Imperative to Pure-Functional and Back Again: Monads vs. Scoped Continuations By Ron”

You're right, I'm sorry -- I meant language-level abstractions/syntax, not extra-linguistic features that may be associated with a language or a runtime such as performance, monitoring, GC, code-swapping etc. We know that extra-linguistic features make a lot of difference. In fact, it was this exact realization (namely, that extra-linguistic features make a much bigger difference than syntactic abstractions) that contributed to Java's success. Gosling: "It was clear from talking to customers that they all needed GC, JIT, dynamic linkage, threading etc, but these things always came wrapped in languages that scared them" (here 11:30-17:00) Brian has his own takeaway in the talk, but mine…