There's an old saying among military planners: 'Amateurs discuss tactics, professionals discuss logistics'. I'm not exactly sure what the analogy is with language design, but it's certainly 'Amateurs discuss syntax' because boy, do they...
I feel that was a (well-deserved) swipe against this subreddit :D
Well, you have to admit that a lot of people still for some reason care about the exact syntax details and with the straight face discuss that as one of the reasons to prefer one language over the other.
That is insane, considring the fact that AI now writes a lot of code.
For folks watching, for copyright reasons the full Steve Jobs video clip couldn't be included in the YT version. So here's a link to the original clip. Which, as I mentioned, could have been my whole talk.
Always a pleasure to hear the inside story of the Expert Group. I think the core messages can also be extrapolated to "how to be a good steward of the system you own".
I think that whatever languages come next, the reputation of caring about users and the ecosystem as a whole is not something you can earn. It just takes time, and there is no way to accelerate it.
I really enjoyed this perspective from Brian Goetz. And honestly, the more I think about it, the more I feel that Java's biggest strength isn't just what it has added over the last 30 years. It's also what it has deliberately chosen NOT to add.
Think about it:
Knowing when to say no is just as important as knowing what to build.
Backward compatibility isn't just a constraint. It's a promise to millions of developers and businesses.
Every new feature comes with a complexity cost. Someone has to think about that cost for the next 10, 20 or 30 years.
As someone who has spent years building enterprise systems with Java, these ideas resonate with me deeply.
In fact, they're a big part of why I'm writing my upcoming book, Buzzing Java. I want to explore what Java's 30-year journey teaches us about building systems that people can trust.
One thing I'd love to discuss here:
Do you think Java's greatest strength is the features it introduced, or the discipline with which it evolved without breaking the past?
I'm genuinely curious about how other Java developers see this.
I will answer! It is both! The discipline forces us to do better versions of the features we introduce. It is shocking how often you can do better by just saying “not good enough yet.”
That's a great point, Brian. The phrase "not good enough yet" really stands out to me.
I think there's a big difference between rejecting an idea because it isn't good and pushing it further because it has the potential to become something much better.
As someone who works on enterprise Java systems, I can relate to this. Sometimes the hardest architectural decision isn't choosing an implementation. It's recognising that the current solution, even if it works, isn't good enough for the long term.
Perhaps that's one of the reasons Java has managed to evolve for three decades without losing the trust of its ecosystem.
Agree! That's precisely why I enjoy listening to people like Brian Goetz. There's so much engineering thinking behind decisions that might look like simple syntax changes to the rest of us.
EXACTLY what I am thinking of. Java been the best following such discipline that many other languages fell into not following even fraction of such discipline.
I agree. I think the real achievement is maintaining that discipline while continuing to evolve. Any language can introduce new features, but doing so without compromising the ecosystem built around it for decades is a different engineering challenge altogether.
Isn't it both, adding features compatible not just with existing code but with the existing design? (If you follow the expert group lists, see the years of thought that goes into each feature.)
Absolutely. And I think compatibility with the existing design is an equally important part of this.
It's not enough for a new feature to work with yesterday's code. It should also feel like a natural extension of the language rather than something bolted onto it.
What fascinates me is the amount of thought that goes into decisions that most developers will never even notice. That's probably a sign of good language design.
Why would adding structural types/functions add burden to developers?
Structural types can coexist with nominal types. If one wants to keep using CharToObject<T> fine, another class to shove into some commons/utils project of the codebase.
While I agree that some stuff are meant to fit in the context of a language and doing it in java would be clumsy, others are well estabilished and java is just lagging behind.
It doesn't take a phd to implement null safe navigation, it is easier than pattern matching. Is this a case of overthinking or "wanting to do things differently?"
As for budget...IDK, Oracle's jdk budget is probably the largest out there in programming language investment landscape. Factoring out the VM part, which must be huge, I guess what is left for the Java is still significantly bigger than what kotlin, scala, elixir, etc, have at their disposal.
I like Brian's defensive/phylosophical approach to language evolution, yet sometimes it feels like he is THE GUY hindering the progress. Is he just a frontman figure that echoes the consensus of other Java Architects or is he a dictator that has the last world of what (not) makes into the language?
34
u/JustAGuyFromGermany 20h ago
I feel that was a (well-deserved) swipe against this subreddit :D
30
u/brian_goetz 19h ago
For folks watching, for copyright reasons the full Steve Jobs video clip couldn't be included in the YT version. So here's a link to the original clip. Which, as I mentioned, could have been my whole talk.
https://youtu.be/7kZ0zoDYOmM?si=F2cqcL01JDVDNLPf
6
u/TheStrangeDarkOne 22h ago
Always a pleasure to hear the inside story of the Expert Group. I think the core messages can also be extrapolated to "how to be a good steward of the system you own".
4
u/mipo256 20h ago
I think that whatever languages come next, the reputation of caring about users and the ecosystem as a whole is not something you can earn. It just takes time, and there is no way to accelerate it.
12
u/pradeepngupta 22h ago
I really enjoyed this perspective from Brian Goetz. And honestly, the more I think about it, the more I feel that Java's biggest strength isn't just what it has added over the last 30 years. It's also what it has deliberately chosen NOT to add.
Think about it:
As someone who has spent years building enterprise systems with Java, these ideas resonate with me deeply.
In fact, they're a big part of why I'm writing my upcoming book, Buzzing Java. I want to explore what Java's 30-year journey teaches us about building systems that people can trust.
One thing I'd love to discuss here:
Do you think Java's greatest strength is the features it introduced, or the discipline with which it evolved without breaking the past?
I'm genuinely curious about how other Java developers see this.
1
u/noodlesSa 18h ago
I do have a lot of ideas about where Java should go and what it should do. That's a fact.
-6
u/flawless_vic 14h ago
Why would adding structural types/functions add burden to developers?
Structural types can coexist with nominal types. If one wants to keep using CharToObject<T> fine, another class to shove into some commons/utils project of the codebase.
While I agree that some stuff are meant to fit in the context of a language and doing it in java would be clumsy, others are well estabilished and java is just lagging behind.
It doesn't take a phd to implement null safe navigation, it is easier than pattern matching. Is this a case of overthinking or "wanting to do things differently?"
As for budget...IDK, Oracle's jdk budget is probably the largest out there in programming language investment landscape. Factoring out the VM part, which must be huge, I guess what is left for the Java is still significantly bigger than what kotlin, scala, elixir, etc, have at their disposal.
I like Brian's defensive/phylosophical approach to language evolution, yet sometimes it feels like he is THE GUY hindering the progress. Is he just a frontman figure that echoes the consensus of other Java Architects or is he a dictator that has the last world of what (not) makes into the language?