Postcards from the Peak of Complexity by Brian Goetz

The Java platform has added many major features over the years -- generics, lambdas, modules, virtual threads, and others. Each of these is a bet-the-platform effort, in that a mistake could mean permanent damage. While each feature is unique, such decade-scale evolution projects often have surprising structural similarities. In this talk, Java Language Architect Brian Goetz offers some insights, war stories, and lessons learned from the development of several major Java features.

[@vlahunter]

Does not matter if Brian Goetz covers a technical topic or a high level. He always delivers and he is a treasure for the Java ecosystem. Thanks for sharing this!

[@Neo-xe6ty]

very wisdom idea, thanks, Brian

[@tobyzieglerrr]

Java itself is fine, has developed quite good in recent years. But the framework ecosystem, especially Spring, is a complete antithesis to what is said about complexity here. Still rather be on the JVM than doing that C# .NET stuff... these kids are going places.

[@AntonArhipov]

I don't think Spring is so unbearably complex, rather it has evolved quite impressively over the 20(!) years managing to stay relevant. But there isn't a single framework and a single language on the JVM, right? ;) (Kotlin, Ktor, wink-wink)

[@tobyzieglerrr]

@@AntonArhipov As is said, Java itself and the JVM is ok, borderline very good even. But having worked with go lately and some very lightweight frameworks in that ecosystem, i beg to differ. Spring is unbearably complex at places. But hey Java and Spring still pay my bills, and i get stuff done with it... it's just the fun has gone for me.

[@AntonArhipov]

@@tobyzieglerrr I know the feeling.