Arama Sonuçları: "#Javaone"
20 sonuç
“Lombok is like cocaine. At first, it feels awesome, but after a while, you regret your choices.” I heard that quote at JavaOne last year. It made me laugh back then. Today, during the fireside chat with the Java architects, it came back to me. Brian Goetz, Ron Pressler, John Rose, Alex Buckley, Dan Heidinga, and Paul Sandoz were answering questions directly from the audience. I got the impression that these discussions are not about quick wins. They’re about long-term impact. One Topic was: Java Modules Why aren’t they widely used? The answer was refreshingly honest: Adoption is hard because the surrounding ecosystem isn’t where it needs to be—especially build tools. And that led to the obvious follow-up: Why doesn’t Oracle just ship a build tool with the JDK? The answer, implicitly, was just as interesting: Because their time is better spent on things only they can do. The JDK, the runtime, the language—those are areas where no one else can step in. Build tools? That’s something the community can own. Another Topic was: Streams and performance. There’s often this perception that Streams are “slow.” But the nuance matters: The performance gap shows up in specific edge cases—not in everyday code. And the design choice behind Streams was very intentional: Favor code that developers can read, understand, and maintain. For most applications, that’s the bigger win. What’s interesting is where things might go next. With Project Babylon, there’s a path to optimize these patterns further—without forcing developers to rewrite everything. Write clear code today. Let the platform get smarter underneath you over time. ...And then there’s Lombok. That quote from last year still holds up because it captures a tension many teams feel. Lombok helped fill gaps in the language. But it does so by stepping outside of it. Now that Java itself is evolving—records, pattern matching, and more—the need for those workarounds is shrinking. What stayed with me most today wasn’t a single feature. It was the way these architects think. They’re not optimizing for the next release cycle. They’re thinking in decades. We’re in good hands. #JavaOne
🇧🇷 Brasil bem representado no #JavaOne. Comunidade ativa, troca constante e participação em discussões técnicas relevantes. É assim que o ecossistema evolui: com prática, compartilhamento e construção conjunta.
