Thank you for that nice presentation. I rly like the detail of history you put in the intro, helps me to understand the point of view. Hot reloading, *so hot right now !*, would be nice if there would be a feature that quarkus talks to the frontend and would auto reload it I will test quarkus for our env.
In my point of view Quarkus now is performent but it follows the same path of Spring: it hides the magic behind extensions and we poor developer will have to read how those extension works instead of dealing directly with the core behind the magic. I don't like spring because of that. Quarkus is doing the same unfortunately.
"As a Java programmer you're not used to edit, save, refresh" PFFFT LOL, this guy... I've been doing that for the last 10 years with Java... the technology is super-cool on its own, stop trying to make it look better, because you're achieving the opposite... it makes it look old to me. Also, "automagic" stuff is bad... it usually means there's bloat behind that "magic" (i.e. Spring).
I hate "automagic" too but based on the documentation I think Quarkus doesn't use spring under the hood. It uses vert.x which is built on top of netty and it also follows more of that vert.x toolkit approach than the framework approach of spring which will probably mean less bloat.
Autowired is automagic. Quit Java if you don't want automagic. Anyways, Quarkus is only magic in dev mode. All that magic is done at compile time, and compile time only. When you run the app in prod, there is no more magic. That's why it's actually not bloated like Spring
Amazing!!!! Killer framework for Java. Time to reconsider java again.
It is a great presentation to get familiar with another compelling framework to compete SpringBoot
Sir I love ur energy ur content delivery mode ...u r awesome super hope ...
Thank you for that nice presentation. I rly like the detail of history you put in the intro, helps me to understand the point of view.
Hot reloading, *so hot right now !*, would be nice if there would be a feature that quarkus talks to the frontend and would auto reload it
I will test quarkus for our env.
cold start is a very important problem when it comes to lambdas, I think its has good potential to compete with spring boot
there is high availability in the cloud. you can restart quarkus nodes everyday without downtime
Cool, that all i looking for.
Quarkus will it support only serverless architecture ?
Not at all, it's focused on cloud-native apps in general. Microservices are very good supported as well.
👏👏👏👏
I think I "kind of" understand all this.
In my point of view Quarkus now is performent but it follows the same path of Spring: it hides the magic behind extensions and we poor developer will have to read how those extension works instead of dealing directly with the core behind the magic. I don't like spring because of that. Quarkus is doing the same unfortunately.
If you don't like magic you should never have considered the boilerplate oriented language (Java) in the first place.
@@FADHsquared maybe you are right but I was young and didn't choose. So what doesn't have magic? C? C++? Which one do you recommend me?
"As a Java programmer you're not used to edit, save, refresh" PFFFT LOL, this guy...
I've been doing that for the last 10 years with Java... the technology is super-cool on its own, stop trying to make it look better, because you're achieving the opposite... it makes it look old to me. Also, "automagic" stuff is bad... it usually means there's bloat behind that "magic" (i.e. Spring).
I hate "automagic" too but based on the documentation I think Quarkus doesn't use spring under the hood. It uses vert.x which is built on top of netty and it also follows more of that vert.x toolkit approach than the framework approach of spring which will probably mean less bloat.
If you use JPA/Spring/CDI etc you are using "automagic" stuff - unless you are using pure Java you are using some sort of "magic"
@@boemioofworld yes, make sense
Autowired is automagic. Quit Java if you don't want automagic. Anyways, Quarkus is only magic in dev mode. All that magic is done at compile time, and compile time only. When you run the app in prod, there is no more magic. That's why it's actually not bloated like Spring
Feel free to skip the first 4 minutes, just blah blah blah