Bootiful Spring Boot 3 x by Josh Long
ฝัง
- เผยแพร่เมื่อ 6 ก.พ. 2024
- Spring Framework 6+ and Spring Boot 3+ are here, which means new baselines and possibilities. Spring Framework implies a Java 17 and Jakarta EE baseline and offers new support for building GraalVM-native images and a compile-time component model in the new Spring AOT engine. It also features a new observability layer, declarative HTTP and RSocket clients, preliminary Project Loom and CRaC support, ProblemDetail support, and much more. Developer productivity is second to none with first class support for Testcontainers, Docker Compose, and live reloads. Spring makes idiomatic use of the latest Kotlin features like coroutines and extension functions. Join me Spring Developer Advocate Josh Long (@starbuxman) and we’ll explore next-gen Spring together
- วิทยาศาสตร์และเทคโนโลยี
![[VDBUH2024] - Josh Long - Bootiful Spring Boot 3.x](http://i.ytimg.com/vi/3SiYK0BWr0M/mqdefault.jpg)
It's the best time ever to be Spring Developer because we can hear Josh speeches. I love you dude.
I can listen to Josh Long all day long without getting bored!
Seeing Josh Long name I clicked on the video
He’s the goat
Josh, you're one of the best tech speakers out there. Just amazing. I loved this! ❤
Always great to listen to Josh.
Thanks Josh
Love Josh for his way of presentation. It is fun but still very interesting!
This is some new kind of standup for devs, loved it.
It's been more than 6 years since I last used SpringBoot, and I didn't realise that Spring Boot has changed so much since then. Excellent presentation, can't wait to try out these new tools and features!
I'm here to know about Spring boot and I know about Josh now 😊
No doubt, Josh is the best guy to present this....
I don't want the sad look in my children's eyes if they find out I'm still using Java 8. :D
Amazing! Thank you Josh!
Thanks Josh! Your speech was really bootiful!
Been using quarkus for the past 1 year and a half and can say battling with native image builds is painful, nice to see spring provides a way to overcome the those issues
Spring and Josh rocks as awlays!!!
I was admiring Josh the moment he started writing code, at 32:44, I became his fan :D
Great talk, thanks!
bootiful as usual
Pure excitement 🤍
it was great. thank you
Great talk! Glad to learn new things!!!
* Goes back to jenkins pipeline still running the job for our java 8 app (it's cemented now and will never update) *
super cool talk!
Great !
you are saint sir
Thx josh, the problem with graalvm thats is not scalable if the app is getting more load there is no jvm to optimise the results.
awesome
any way we can use async await with spring reactive ? method callbacks are pretty un maintainable
27:51 var makes the code less readable. Set observed = new ConcurrentSkipListSet() would have communicated that you really just want a Set at the end of the day and you are not going to call some special method of this very specific implementation of Set (at least the code YOU write isn't directly going to call some special methods) .
There's no significance in such a hint. Yes, I can infer from what you suggested that even though you are using a ConcurrentSkipListSet, you only want it for its behavior and not the methods that specific implementation provides but even so, does this matter at all? I'll have to read the rest of the code anyway so there's really no mental overhead when it comes down to check how you're handling that set.
I strongly believe that the restrictions Java has imposed upon the var keyword are more than enough to cover the cases where it would actually become less readable code, anything else has very little significance and falls upon personal preference.
who is this person? does he have a channel or something? the way he talk and describe the things is awesome and want to follow and hear more about his lectures
literally the very first thing You see on the screen is all the info about his social media ;)
Graall VM configuration problem would have been a non issue if JAOTC continued
Good to see Java catching up to where scala and kotlin were 6 to 10 years ago :-) Jokes aside, great talk! Lots of exciting developments in the Java world.
It is like that by design. Scala, Kotlin are successful experiments. The successes get absorbed into Java after being field tested for years. Java ecosystem prefers stability over moving fast and breaking things. What is the market share of Scala today? Kotlin owes its user base to Android. Google wanted to avoid more lawsuits from Oracle, that was the main driving force behind Google adopting Kotlin for Android.
Java slowly becoming kotlin
So ?? Ocaml 🎉
How fast is jython
33:42
I'll just pretend not seeing all the enthusiastics giving free pro tips of "just use kotlin" like their advice is so groundbreaking that no one knows or uses it already.
Java Looks Much Better.
JAVA is many things, but fast to startup it is not.
CRaC: Hold my coffee
With native image builds it is extremely fast
Nothing extraordinary here when he said for Go to go away then waited a minute and used gigabytes of ram to build native image made me laugh
You've presented nothing but a mere integration with OpenAI, where annotations are at the top, nothing more. I don't see any grounds for admiration here, and I'm trying to be pragmatic. The solutions you're talking about were already available in Python a year ago
Guess when spring integration with AI was announced.
Who the heck is this much excited about doing Java in 2024? At least choose Kotlin with Spring if you can't do C#. 😂
Kotlin is great. But did you watch the video? I'm a kotlin GDE. I love Kotlin. I've done variations of this talk with Kotlin over the years, too. The thing that's interesting is the JRE runtime, which benefits Kotlin (and Scala and Groovy), too. And if you're a Java dev but want non-blocking IO (without the verbosity of the async/await in C# or suspend in Kotlin), then Java 21 is for you. If you want pattern matching (on par with Kotlin), lambdas (tho not quite as lovely as in Kotlin), auto typing (`var`), multiline strings, switch expressions, data classes (records), sealed and final types, and much more, then you could choose Kotlin, OR Java 21. and that's a nice situation to be in. the more the java and the jvm improve, the better off everybody - including kotlin - is.
Lol go back to your cs 101 intro to python class
C# over Java? Neah…