.NET Developer tries Java Spring

.NET developer tries the Java Spring framework. Looking at the daily life of a Java developer & some beans.

👉 Try Rider
RD5K9-4TXXW-KMV3G-NYWSF-3ZSTP

#aspnetcore #spring #java

[auniquehandle]

"the fuck is a bean"
same bro, same

[rubenvervaeke]

Don't have experience with Java & Spring and immediately starts out with Spring Security, that's brave my man.

[YariRu]

The secret is to use very long class names like

[yeumkyuseok]

Im amazed at how you could code on the spot in such an unexperienced framework/environment this flawlessly!!

[Toradoshi]

Aspect Oriented Programming a.k.a. introducing bugs under the hood is the backbone of Spring.

[unhandledexception]

I honestly love watching this guy, his humour just brings to life any technical topic ....awesome channel
;-)

[oumardicko]

For any JVM related stuff, i use kotlin. Easy to use, innovative, no complex BS or verbosity. Kotlin has a backend framework called ktor and i can say, the language has some of the best developer experience i have seen.

[IvanRandomDude]

I work with both. Aspnet core is definitely easier to master and is innovating faster than Spring. Spring is huge, has like 50 different sub-frameworks and is being developed slower. I also like EF core more. Spring JPA looks great but as soon as you need complex queries it becomes a mess. Nobody even uses it for complex stuff, for complex queries we usually use jOOQ or some other library (they basically use LINQ-like syntax to build queries)

[Narezaath]

The one-liner authentication you've heard about is probably the simplest Spring Security authentication, which is just adding the library to your Maven/Gradle config and maybe an annotation. That is all, like, literally. At the start Spring notices you want authentication, sets it up for you, provides you with a default user and password and you can use those to authenticate. Done. If you want to configure it further then yeah, you'll have to jump through some hoops, like what you've experienced. You first specify the route either explicitly or by a matcher, then decide what to do with it: permit access without authentication or allow only authenticated users.
JPA stands for Java Persistence Api, which should tell you what it's for. :)

[petru-cristianboza]

I'm not sure how asp looks like.
I do agree on the security part, it seems a bit hard, sometimes like "whack a mole"
But the ORM stuff can be done a lot better than what you described here with just some more insight on the framework.
For complex queries we use JPA Specification which allows you to create queries easy to maintain and modify.

I would agree on the fact that it has somewhat large learning curve, especially if you spend a day on it, but after some time, things do become a lot better :D
Thx for the video

[lucasmontec]

Also, you can write SQL in attributes (annotations) of those query methods. Lifetimes are defined by the type of "service" you are creating. Repos have a lifetime, services have another... All is registered automatically on startup.

[younevilletube]

EF also lets you have setups without having migrations (some default templates do it). If you are just querying all data you wouldn't have to use LINQ in EF either

[noname]

From the init of my developer experience I worked mostly on java and i learned dotnet 6 this year... dude i'm never wan't to back to use java.. the difference is huge.. in every single aspect, asp net and entity core are waaay better than java + spring or another huge rare framework of java

[wlockuz]

The only thing stopped me from going completely insane when I used to work with Spring was Intellij IDEA

[kutilkol]

Man you're good! That was some quality content, thx

[fudosker]

It might seems like complicated staff, but only on start of the project...
Now you can use spring boot which comes as part of code that performs basic configuration at runtime

[sudarshanshah]

Java is love. Spring Boot is expression of it in best of sense.
Everything is easy to configure and conventions are easy.
Anything can be integrated with it with ease and seamlessly.

I am proud to be a Java Spring Boot developer. It's breeze to do development with Spring!

[coffeeable]

Actually, I think EFCore is much better.
- I don't think these magic queries will be suitable for complex real scenarios.
- I like the idea of migrations, I need to know how my class chnges will be translated, like if I rename a property will it drop the column and create a new one or it will rename the column.
- many to many is much cleaner in EFCore.
- The Generics in java is just converting to objects under the hood, the language design is worse than C#.

[JonneKleijer]

Insightful! Thanks for sharing your insights.

Could you do a similar video on NestJS?

[GavrilosZ]

im java dev and u are doing great trust me :P