If you configure youtube to use the HTML5 player, there's an option to watch videos at 1.5 or 2X speed..

key points I remember:

* Java isn't dead, or dying; it's still among the most popular languages and growing, based on analysis of data from github, stackoverflow, and mailing lists

* It doesn't command the same relative amount of mind / marketshare as it did in its heyday, but that doesn't really matter; the market is bigger, and it's still growing

* there is a significant correlation between programmer age and use of Java

* ease of initial installation is an underappreciated factor determining which technologies get adopted and become popular

Is complete transcription available somewhere?

You should take that time, it is interesting and deserves its upvotes. Summary: Java is not dead.

He is saying that he can't build the case that Java is dead because the data says java stays popular, even though it has peaked in popularity. Data including usage on github, stack overflow, mailing list traffic and job demands.

What I found to be interesting is his part "easy wins" and how that was and is a challenge for the Java community, including a nice example about postgres on debian systems (which was not easy to install as it was not in the repositories).

The most concerning sign that Java is dead are the frequent articles purporting to show that Java is not dead.

I agree, though Java is far from going into decline (I think the salary average may be a large contributing factor), these kind of posts always feel like an indicator of things to come.

Speaker is an analyst and uses several numbers (Tiobe, mailing lists, Stack Overflow, GitHub) and examples (Netflix) to show:

a) that Java is over its peak because it has to tolerate much more languages (JavaScript, Ruby) then in 2006

b) that Java is not in decline, but at least sustaining its popularity and if you include Android you could say the 'Java semantics' is growing.

Speaker continues with some examples of frictionless technology stacks/products, and argues that Java is not that. To sustain growth it needs less complexity, better package managements, compatible licensing, low cost Java hosting.

Finally, some languages got popular by the web frameworks (e.g. Node.js, Django, Rails). But Java web frameworks are too fragmented (due to its long history as a popular language and platform). Java should take its cues from those.

Man is that last point true. Java sorely needs a neat, clean, and simple web framework. There is absolutley nothing inherent to the language that dictates that it cannot support such.

Is there really a place for a simplified Java web framework, when there's plenty of options that run atop the JVM with full access to JVM libs? (Grails, ColdFusion + several MVC frameworks, etc)

Yes.

EDIT: BTW, I think your question actually answers itself. That is, the reason there is such a proliferation of MVC frameworks is that they largely have been found lacking, so someone sets out to create another (presumably simpler) one. Simplification is almost always the motivation.

Likewise with Grails and others that run atop the JVM (which frequently even encourage adoption of completely different languages).

All of these are testament to the dearth of a clean, simple, elegant Java web framework.