About this talk
This keynote discusses the evolution of Java over its 30-year history, highlighting key moments and contributions from its inception to today. The speaker explains how Java has adapted through various technological shifts, including desktop applications, cloud computing, and the recent surge of generative AI applications. Emphasizing its community-driven nature, the talk outlines the importance of collaboration and contribution to the Java ecosystem, urging developers to participate in discussions, contribute to open-source projects, and engage with local Java user groups. The speaker also touches upon modern innovations within Java, such as new enhancements in JDK26 and the growing intersection of Java with AI technologies. Overall, the keynote reflects on Java's legacy while projecting its future shaped by collective efforts.
Full transcript
[music] Hey. Hey. Hey. >> [music] >> Welcome to JCON. Wow, 30 years of Java. Actually, more than 30 years of Java. I'm pretty nervous to talk about such a an important topic for a technology, but I think for all of us here in the room would help me a lot to understand, are you using any other technology as a developer besides Java, can you please raise your
hand if you do that? Yes. some more. There's a reason for my question and I'm going to detail about that in this um in this keynote. But who am I? Well, 30 years ago and more than 30 years ago um I was this person and um this grumpy little kid here. Um so when Java was starting to being thought of as a programming language, I was this
um this little lady. And some people are like, "Oh, but the child doesn't smile." Well, I'm from Eastern Europe and that's how I manifest joy. Uh, and secondly, uh, I would like to share the background be uh, for this because I remember the whole thing. It stayed with me. So, my parents really wanted memories with their little daughter and they wanted to take pictures like not digital
back then. Uh, so dress her up in a dress, right, to look cute. The problem is that I like a lot to I liked a lot to like play uh in the dirt to dig in the dirt with my friends. And that that kind of outfit stops you from digging in the dirt. So me back then as a kid thought, you know what, they want pictures. I
want to play. I'm going to give them grumpy memories so that that's how they remember me and maybe they don't make me wear dresses again. And well, look at me today. And nobody made me. No parent was there to tell me this. I learned on my way that well it's better to or better you have to feel comfortable in what you're wearing. Um so that was tiny
me. But in another part of the world there was a gentleman James Coslink that was going to the office and he was thinking to much more complex things than playing in the dirt uh like I was at that point in time. He was imagining a programming language, one that is simple, objectoriented, distributed and bunch of other things. But that programming language, what you like really need to
take from this slide is the first thing that he says about it is that it has to be simple. And the reason why it has to be simple is because that programming language probably it's going to be used by humans that work in the same team. And ideally they have a great language that they talk to between each other but also they talk to the computer. And
I think that has been a goal with programming languages all the way to make them simpler for us humans to talk to the computers. Now in 1992 the programming language that was envisioned back then uh it was called Oak because James Gosling was seeing all the time an oak outside of his office window. And what use case does Oak served back then? Well, Oak was serving um
a use case called Star 7. And well, Sun Micros Systemystems had created a special engineering team. And James Cosling was part of that team to prepare for the next wave of computing. And that team decided to focus on the convergence between computers and home entertainment systems back then, TVs probably, right? Um and that system star 7 you can think about it about the precursor of internet of
things idea that is happening nowadays. Uh some call it a remote on steroids but was the center of that system. So it was a remote with a very nice screen. It had a lot of ports. Remember when we were looking for computers that have a bunch of ports attached to them so we can connect them to more things? That was pretty much that but in a smaller
smaller pace. And in that 1992 use case, there was somebody else. There was this merry jumpy little guy um that was introducing you to the capabilities of Star Seven. And this jumpy little guy nowadays, we all know him as Duke. Well, probably you haven't heard about star 7 except from the history lessons like I did because star 7 itself did not become a commercial success. But what
it happened is that it laid the groundwork for future innovations and also demonstrated the potential of touchscreen interfaces. Also, the software concepts that were explored in the star 7 project paved the way for Java. on May 23rd 1995 that's when Java was probably announced for the first time. Now the efforts of that um of the project green transcribed into the main talk the main character of this
talk today and the slogan that you see here probably you've seen it before. Can you please raise your hand if you've seen the slogan before the day of today. So you know it you know it was run right once run anywhere. And this one described the software benefits of using the Java programming language. And you probably know it even today. Refers to the fact that compiled byte
code from Java source code can run on any system with a compatible Java virtual machine. And from there from 1995, we got to Java everywhere on multiple devices and we got to dream about Java in so many different ways. And the way that I dreamt about Java when I was in university and I actually put in an application was to actually use Java to control robots. You
can find me at the Oracle booth and I can tell you more about how I did that back then. But most importantly, apart from Java everywhere, Java has become a skill working across many platforms, empowering a lot of developers. Now, how could that happen? Like how can Java work across so many platforms? Well, Java came out in the '9s, mid '90s, and I think we should reflect
a bit about the changes that we saw uh in the technology shift. So, probably many of you record the desktop applications. Then we got to client server desktop applications, web apps, and we all love web apps, mobile applications. Then it was cloud applications. S era, come on. Cloud native Java. We have heard it. We have seen it. And it even is today, right? And now starting 2022,
we're experiencing the generative AI applications era. But Java was there since its appearance and evolved through all these shifts. Also, it evolved through the way that it was supposed to be deployed. Evolved from mainframe to on premises to data centers to containers. In case it's on on premise, for example, to hybrid to clouds and more. So this is quite impressive to survive so many shifts and to
adapt all the time. But not just the technology itself and the code has evolved. The Java logo has evolved. Duke has evolved. It has come in different shape and sizes and look it is even eating popcorn very suitable for the cinema today. But one very important change that happened in the technology and that's something that we are going to have as anniversary in 2026 all of us
is that in 2006 that Java 1 in May 2006 there was an announcement that Java will become open source and that so that happened almost 20 years ago in May we're going to celebrate 20 years since Java was announced to be open source. Now the first code drop it happened in November 2006. So the announcement was made the actual code drop that you can see the code
it was in November 2006 and since then well we all got to witness the thoughtful evolution of Java. It preserves what works and respects existing systems hence the users and their knowledge. Java values stability but also supports change when it strengthens it and lasting changes respect the foundations they are built upon because progress is not disruption it's how we maintain harmony over the time for all the
libraries frameworks tools applications and everything that you build out there so responsible innovation is one grounded in experience and what have we done Well, over the last 80 years, we have broken large problems down, pain points, get real world feedback from you through preview features, early access builds, uh push projects like ZGC, Amber, Panama, Loom, Valhalla forward. And we've done all this by staying true to our
commitments of security, stability, and backwards compatibility. there's a something that couldn't fit in a slide. Unfortunately, there's a Java universe of libraries, of tools, frameworks, and everything that you build upon. So, it's hard to fit all in in that. But this universe of possibilities is amazing because it continues to expand. Well, sometimes some frameworks may be discontinued, but the universe continues to grow, and that is thanks
to you. So how do you become part of the story? When we get hired, we get hired for our skills and we get a job title probably most of us because this is how organizations work. But what we're doing in our job being code, specifications, architecture, diagrams, interpreting, understandings, you name it. Uh well, that's where our individuality shines. I believe that repetition builds strength, but uniqueness gives
it meaning. And well to power all that you need some programs around a technology and the programs around Java well you can think of the open JDK the open sourcing of that and what it brings to it but also the JCP the Java uh the Java sorry I forgot the acronym the JCP is the mechanism for developing the standards tech standard technical specifications for the Java technology
also we have Oracle academy which is to prepare students for careers in tech and also Oracle University to develop job ready skills and certify expertise. So all this is there but also for you mean Richard earlier mentioned Java user groups. Java user groups are the places where we get together and we can talk about Java but also the connection to other technologies. Hence my question like you're
using anything else at work besides Java because we want to discuss how the universe can expand and be bigger and better all through collaboration. But to discuss a little bit more about how the universe expands I would like to welcome on stage to discuss all this with a few guests of mine. So I'd like to ask here next to me Andres Almirai come and dress [applause] Brian
Vermeier [applause] and Bruno Souza. So maybe you've seen them as speakers at at uh the conferences, maybe you've seen them welcoming you at this conference, but just give a brief introduction to who you are, what you do and so on. So people would know you just very brief because I have things to say during this keynote. [laughter] >> So my name is Andrew Samurai. Hey everybody. Um
uh I I've been uh working with Java since the beginning since May 23rd. I was in college and I keep working it because I love it. >> Um my name is Brian Veir. I'm from the Netherlands, work for with Java for almost 20 years. Uh run the Netherlands Java user group, Jall, JSpring, etc. And I'm happy to be here. >> Hey, hello everyone. I'm Bruno Sza. I'm
known as the Brazilian Javan man or the guy with the flag. And my goal is to help you for 30 years I've been working to help you to grow your career and become an amazing developer. >> Keep your keep it keep it keep it, Mr. >> So I just want to be very quick about this and the first question is going to be addressed to Bruno. First
question is what kind of mindset and culture do you think that Java encourages among developers? So it's very interesting that you know all this great story uh about Java is that when Java was released in 1995 it was released in the alpha 2 version right uh the first public version was released with the source code for the language for the for the Java VM it was released
with a specification right that allows us to to discuss uh you know how to implement Java in different things and was released uh with a compatibility test right that other people could implement and uh Java, right? So, so from the very very beginning, Java was made to be collaborative, right? So, lots of people, you know, imagine right there uh you know, we announc JDK for example, that
came in 2006, but in 1995, uh that's three years before the open source definition exists, right? So, Java was already released with the source code. So, we could have at that time, you know, we could learn from the source code and you guys know how important that is. And then not only you could learn from the source code the the the the license allows us to experiment
to change uh the VM to change the language to experiment things and to discuss that right it did not allowed us to to to kind of redistribute that's was the kind the missing part for the open source part right but allows us to to have a discussion and that's why in you know in in 1996 97 we had explosion of Javis groups right so so Java this
group that I run it started in 199 98 right so to the very very beginning let me just ask you here who was born uh before 1998 okay lots of people that's good right so who was a professional at that time very few people [laughter] right so know so when you guys were you know so so so you you guys start like like your picture right when
you're very young uh we're already discussing and building communities around Java so that's the mindset said right ours was the mindset was community and working together and collaborate. >> Thank you Bruno. Well speaking about collaborations and contributions. Well I would like you to ask Andress what contributions you feel that had real impact on you but also on the Java community. >> Well I have to start with
the first one. So, so back in the day, so you can tell a bit for the gray hair, I I needed to uh so spring MBC did not have a JSON view and there was no JSON library that you could use. So I decided to create my own. So I thought maybe I can make this as an open source thing. But in order to make it happen,
I was consuming another dependency, Apache Commons lang, which some of you were probably aware of. And there were some issues with handling byte arrays. I needed for worldw. So instead of just keeping it to myself, I talked to the developers and say, "Hey, this feature may be missing. This particular method is not working properly. Uh, could you guys fix it?" And they said, "Yeah, we can, but
what about if you could send us a patch?" So that was my first ever contribution to an open source project. I was not thinking about that. And it was actually a tiny one. And then I kept working on that and I found another thing and another thing. And just like the proverbial snowball, just things kept rolling down the hill. and suddenly now I'm find myself 20 years
later as a producer of many open source projects. I was able to find and to make a lot of friends uh because of that. So a tiny contribution will take you a long way. So I know that working on open source is not for everybody but at least I will say give it a try. Maybe it's a small patch, maybe it's just filing an issue. Maybe you
could go all the way and create your own projects or just uh make a really tiny contribution. I think that is what really took me the most. Just get it started and then just figure out what happens. Thank you, Andreas. Well, now that's a very inspiring story. Thank you so much. And um yes, I think that many of you in the room uh work on private repositories,
work under NDAs and sometimes it can be frustrated that you cannot contribute to something that's open because you see that there are many constraints about that. However, there's always a way to contribute and there's always a way to help in the Java community and um I think that earlier Bruno has shared it with the Java user groups and volunteering because it's all about how you want to
be um you know how you want to contribute to the to the community. It doesn't always have to be code to be appreciated. Now the third question I want to ask to Mr. Vermier because well I know his passion for security but I've also been to his first presentation which was about functional Java. It was a very fun one and I saw that one in 2018. He
had a packed room in uh in Devox Belgium when I saw that when I uh when I saw first the for the first first time his session. So which framework, library or platform change in Java do you think is the best to represent Java's current relevance for modern development? >> I think first of all the community is the most important one to Java. I mean like like
without the community it's nothing. That's also why we want to be your friend because you can fix open source libraries for me. Um now but but seriously people say Java is old. Java is is for both. But think about how Java has evolved over the last decade or so. Currently in the later versions in the last versions of Java where they are the the the engineers already
thinking about post quantum crypto cryptography which is not a thing yet but will be a thing. So that is already in there. So if people say that Java is old guess again and read what's in the newer versions and I think you can can compare that as well with how the full ecosystem works like who is a Maven user or a Gradal user. So if you install
a package in Maven or gradal the whole ecosystem works in such a way there are blockers there that you cannot just produce a package. Try that with other ecosystems like mpm when they have post install scripts with uh- which which will lead you into uh supply chain security more often than in the Java ecosystem. So from a security perspective Java is a very pretty good language and
ecosystem around that. Lastly, if you look at all the generative AI stuff, everybody is speaking about Python. But guess what? With the libraries like Spring AI, lang chain forj or the caucus implementation, it is even easier to do that in an enterprise level. On top of that, if you look at how the the the folks that are implementing these libraries are thinking from a security perspective on
who how to include guard rails on how to check what's going into your AI, what's going out, what's going into your tools, what's going out. It's easier than to do it in Python. So you can do that in an enterprise level language and you don't have to go to Python which is great don't get me wrong but probably a lot slower and not available for you as
an enterprise developer. So I think Java is on top and Java like and pretty much everybody is is saying other otherwise except for the people that work in enterprise level development. So I think that's a good thing. >> Thank you Brian. Now [applause] a lot of you in the audience are experienced developers. So each of you needs to respond to this last question like how can experienced
Java developers still have impact today in their roles but also in the community. So very quick >> I think the easiest way is you are already here. Talk to people around you. Don't just go for all the talks. They are great, but talk with people in the hallway with each other, in the mentor hub, on the Yava user group. Share even your things that you think are
not really important can be important for somebody else because they didn't experience your problems yet. >> Yeah, I I'm about to repeat the same words. One of the things is that uh every one of you has something to share. It's not about quantity. It's not about size. It's just about even it's just simply saying thank you for that session. Thank you for that conversation or something similar
like that because you have no idea how long those little words of encouragement can go for someone else that is in need of those things. If you want to share about tech, if you want to share about your other passions, also do it. You have a great opportunity today and the next two days here at this event and you can continue to do so at your local
Java user groups or your local meetups >> and Bruno >> okay hard to repeat the whole thing here again right but my suggestion to you is find one person that you don't know and just say hello right talk about your project talk listen to what they want they want to say and uh and do this with with everyone around you right so so you can meet them
uh you know I'm sure there's someone near you right now that you don't know, just go ahead and say hello, right? Uh but one thing that you could do is uh come talk to these speakers, right? You know, a lot of times uh you know, when the talk finish, there's like five, six people that come talk to the speaker, maybe sometimes more, but then an hour later,
the speakers outside, no one's talking to them, right? And here's one thing that Hines Kabut said once, you know, he said, "I'm a speaker and I'm shy. So when I'm in events, I don't know what to say to someone. I I can say just hey hello talk to me right so I'm just walk around hoping that someone is going to talk to me and then I know
lots of you you look at high and say oh man that's an amazing Java champ I want to talk to him but maybe he's too busy he's just waiting for you to go say hello right and so all of us are like this so come and say hello and a good way to do this of course is come to the mentorship hub uh there's going to be
all day uh going to be uh uh know speakers there talking to talking to you and you can go you can take a look at the agenda at the the website. >> Thank you, Bruno. Thank you, guys. Thank you for sharing the stage with me and for inspiring the audience. [applause] Well, speaking about sharing and contributing, I want to bring something to your attention that also is
about contributing. So, you can contribute to Open JDK. So many people including myself many many years ago I thought that open GDK project although that's open sourced well because I was working on private things I was thinking okay I can never become a contributor there it must be some very smart people that work upon that and maybe I'm not enough to be a contributor there I can
tell you that I am a contributor there today so I want to tell you that when you're new to the open JDK project and you have not contributed anything yet you are a participant. participant means that when you are going and subscribing to the mailing list and you're getting involved in the conversations there because there are sometimes conversations when people discuss how certain feature will be evolved
and you especially you that are very experienced in the audience you have known how that feature worked for you and your teams you can get involved and share like you don't have to say that I'm working on this and that like all the you know private details but just give an overview of your scenario so that we are aware of that scenario when we are thinking about
future about the future and the future. So, but besides this, there are also additional ways to contribute. You can test the early access builds. You can, as I said, provide constructive feedback on that. You we have quality outreach where we are reaching to the libraries and tools that are in the Java ecosystem to let them know that there's been a change that uh has occurred in the
open JDK and that might impact them. So, we ask them to test the early access bills. We write about those and we say, "Hey, this has been introduced. These are why we introduced this change. It's for a benefit, but we also want you to be aware that this has been introduced so that you don't end up like deploying something or releasing something that could affect your end
users. So come to talk to us to our booth about how you can contribute to Open JDK. It's uh very straightforward and easy. Now uh there are a bunch of features in releases and you probably seen them like some features are final features, some features are experimental. So the experimental features are most of the time related to uh the hotspot enhancements. Uh and you probably seen this
very recently that when you need to uh maybe enable a certain generational uh garbage collector, you have to use uh sometimes the experimental flag. So these are the experimental features. Now once a feature based on feedback and of course benchmarks and other stuff is becoming reliable enough the experimental flag is not needed anymore but in the beginning they're experimental. There are also experiments that probably don't succeed
and they become they stay in experimental stage until they actually become a success. So it takes a little longer because we again we want to make it strong and backwards compatible and preserve the stability. There are also incubator modules. So these are APIs tools that one day might be in the JDK. Uh but we need feedback upon them. So can think of incubation like a pre-stage for
preview features. And preview features are features that I would call they're almost done, but we need again feedback to actually consider them done. And if there's something that we anticipate that it's not going to be 100% to the to our uh values to the values of Java then maybe it's better not to release that yet and give another round of preview. Sometimes it can be exhausting and
it can be disappointing. You see oh this again is in preview well or this again is in incubation. Well, we're doing that because we want to have the features ready in the greatest shape possible so that nobody experiences disruption in what they're doing at work. But I've been telling all these because I also want to talk of Java of today and well Java of today is JDK26,
right? And probably some of you have seen Java 26 has 10 JDK enhancement proposals covering improvements in performance, libraries, language, security, and more. So you've seen these things and pro and I've seen a lot of people that focus on the fact that there's these chaps and probably many people received that maybe nothing else was there. Well, there are way more than that. There are thousands of other
issues and enhancements and these are just another portion of notable features in Java 26 and like performance for virtual threads improved a new hairy creature emoji for unicode 17.0 zero support. But altogether with all these features that are being implemented, Java continues to get better, faster, more secure in every release. And of course, uh there are a lot of contributors and I couldn't fit all their pictures
in the slide. Would have been nice. Uh but also I would need to get a lot of agreements, you know, for sharing pictures because we're in EU. We need to like be be cautious about that. So many of those contributors are like you and you trust Java because is a great platform, a pro great programming language when working with it. But it is powered by companies but
is most importantly powered by people that work at companies and not only that want to contribute and make it even better. So again, if you would like to contribute, please stop to the Oracle booth to have a chat with me and my colleagues. But besides making Java, Oracle well also makes other things that help Java evolve. So a bunch of these things are related to Java effects
and its support to the Java platform extension for Visual Studio Code and of course our own flagship framework Heladon. So what about the future? We want to hear about the future, right? Well, future I know a bit about the future. Uh, but I think you also know a bit The future is anchored in present efforts. We've talked about Java technology, about community, about evolution, about connections. But
everything in the platform is connected. It's not just what it is in the mainline JDK that gets released every six months. It's also about the effort of experimentation that goes behind the scenes and we have seen the experimentations being called in different projects. Now some of these projects are dear to my heart because I get to experiment in them myself. So I'm more passionate when I'm going
to talk about them. But um engineering teams like my colleagues at Oracle and also the people that from the previous slide, they find time to contribute to these projects and then once their contributions and experiments are mature enough, they become those types of features that are incubators, previews or experimental features. So this is where the future starts with this innovation here and it's done all in the
open. So all these experiments are open sourced. It's not just the JDK itself but also the other projects that exist around them. All conversations happen on the meaning list. All the source code is open. But moreover, what is the strategy behind this? Because well, Oracle is the steward of Java. So what's the strategy with Java and AI for example? Well, we've seen development in the agentic development
space as well. And for geni we there's tools and services like OCI generative AI like cursor Java vs code extension. Yes the Java VS code extension that Oracle has works with cursor as well. And of course we also like to collaborate with other ecosystems. We frameworks like with Embble Coog uh or Coug Spring AI and more. We also like to embrace libraries and frameworks and HeladonAi has
done that. So, Heladon through its AI portion has embraced Lchain 4j and has done a wonderful job in creating a a seamless library so that you can work together with different AI features. We also like chain 4J itself. We also like Spring AI and my colleagues in the database team, they have probably many times publish a lot of tutorials about how to use Spring AI with the
Oracle 26 AI database. So, give those a try as well. And well, we look into other projects too like Amber, CGC and Panama. But my favorite part is coming now, the controlling part because I would like as a professional to be able to control how a model is being trained and how a model is being worked with, how it's going how I'm going to do inference and
how I'm going to do deployment of that model. has been a dream that I've been passionate about in 2015 when everybody like in my master's degree said how can you want to do machine learning with Java when Python is the best for machine learning and I still still did my paper in Java uh and if you want to you know talk to me more about that come
find me at the booth but I am very excited about the possibilities of training and deployment that I see with the evolutions of projects Panama Valhalla Babylon on and lately with the announcement of the project Detroit and of course we have a few experiments and demonstrations that are are in the Babylon repo and especially we have a few experiments regarding running Java on the GPU through the
heterogeneous accelerator toolkit again come to the booth looking forward to share those but preparing for the future preparing for having control over AI models over how inference with those is working and more needs good learning, right? And good learning comes with good foundation. Knowing Java is a great way to start with having that foundation. Now, there are conferences, there are meetups where knowledge is shared. But maybe
sometimes you're tired to travel or you have other personal matters that impede you to be present at a conference or at a meetup. You're not left behind. Now knowledge is shared through tutorials ondev on Java and learn Java. Insights that happen in the Java platform that the engineers and myself are writing about, they're being shared on inside Java. And of course, there's a YouTube channel where you
can find out more about what's going on in Java, what's new, what's going to happen in the future. And speaking of learning for students, we have learn Java. And in learn java we we have this special place uh called Java playground. This is a browserbased environment where you can run snippets of Java code without the need to download the JDK or use an ID. Now you can
just run a piece of code. It's not an ID 100%. It's just where you can go write some Java code and run it. So if you're eager to test JDK26, you can go to learn Java or dev.java Java because also has JDK uh 26 and the playground and try the new language features or the new core libraries features there. Most importantly, we also have a way for
you to share those experiments. So we have added recently uh a feature called shared snippets where you can just go type some code in in the playground and then with a custom URL you can share that code with others. And the funny thing is, not sure if my colleagues really tested this, but the same snippet ID works between the two playgrounds that is been learn Java and
dev Java. So I think that's a that's a feature. So uh yes, and my manager gets to find out now live. Uh so um surprise surprise but I think this kind of feature of sharing the small code snippets can help you when you want to share an idea with a colleague or can you share about like hey I learned about this thing let me show you how
it works. We also give you examples of how some features work so that you have a way to interact with those new features and you're not like oh my god how I'm going to write a new lazy constant how that API works. So you can find them all there. You can share them and you can share it with us. I mean if you want you can share
them on social media and tag us and see look what I built there. But uh getting back to all that I wanted to say is that the future is if we're help built by us, if we're helping each other and I think that's what everybody that was here on stage wanted to say and all the efforts that we see with Java are there to support communities all
around the world. communities today are represented by developers like you that are in the audience that are asking questions that are come to the booth that will challenge the ideas that will be unhappy with certain features um that are going to pose a very smart question to a certain speaker uh but also developers that contribute and share further their learning with their colleagues and I see that
all of you are relaxed on those chairs so I'm going to do something a little unusual I would like you to stand up Please. Yes. A lot of people listen up. It's good to do some exercise now. Yeah. Yeah. Yeah. Yes. Developers, you know, raising from the chair. It's I know how it feels sometimes. It's hard for me to at home. I want to take a moment
to recognize the contributions that all of you have to Java regardless if it's in the open source and or in the private repos because I was once a developer that was supposed to code only on private repos and look at me I'm here and I'm contributing to Java. So I want for us to applaud ourselves for being part of this community for helping our colleagues and just
for being awesome here. [applause] Thank you. >> [applause] >> You are part of Java's story. What I want to say is that Java has lasted 30 years because it evolved. You can stand or you can just tell sit down. It's up to you. I don't want to like [laughter] impose anything. I just want to impose just standing up. So what I want to say is that well
a technology lasts for 30 years because of the humans that are you know inspired and dream about it about it or at it. For many years I dreamed about it being part of a story and I believe that the future is being built by all of us all of us together collaborating sharing the little that we have. As Andreas said it, you never know the little that
you share today can help an entire world. And well, while you're sharing and having fun, we at Oracle, we're also working on building this Java 1 2027. So stay tuned for more. But until Java 1 2027, I want to thank you for being here today at the this keynote, listening to me. Now go to the JCON sessions, learn, network, and let's shape a better future together. Thank
you. [applause]
