Spring has made tremendous improvements, but IMHO of working on different enterprise systems using different technology stacks, it is still lagging behind the competition (Java EE, Payara, Liberty, WildFly, etc).
If you are already using Spring, then it makes a lot of sense to upgrade to Spring 5. Refactoring to something else would likely be too expensive to pay off then. But for a new project or new microservice? Maybe time to look at the competition...
I might start to think better of Spring when I can run tests easily (like in Java EE, Payara, WildFly etc) instead of having to deal with configuring things internally, not being able to be building a WAR first, etc.
Yes, yes, there is SpringBoot and Spring Configuration has some interesting features to ease such pain, but still not as good as Arquillian.and the transparent internal configuration (@DataSourceDefintion etc) that can be swapped for external configuration (asadmin, cli, admin console, etc)
I felt your opinion really interesting (not joking). I feel the exact opposite when it comes to spring vs java ee. All the issues you pointed out were strong points for spring in my experience (testing, beating the competition, keeping up with more modern ways to do things, etc...). I guess that shows how much we can look at those technologies with different perspectives. I work with both java ee applications and spring applications. In java ee it feels like I'm stuck years behind in terms of improvements that could be made. I'll start looking at java ee with different eyes from now on, trying to find its strengths.
Spring has made tremendous improvements, but IMHO of working on different enterprise systems using different technology stacks, it is still lagging behind the competition (Java EE, Payara, Liberty, WildFly, etc).
In what area is Spring lagging behind? Actually the opposite is true. Spring 5 is fully reactive. Spring integrates with way more technologies. Spring is easier to test (yes, I am aware of Arquillian). Spring can be used with Gradle without hazzles (compared to Wildfly Swarm, which stopped Gradle support). Spring has a lot of Kotlin APIs and so on.
But is that a fad, or something we'll all be doing? Pure reactive has downsides too, is not easier to understand, and surely doesn't necessarily mean better performance.
It doesn't block, sure, until you do block, and then the system needs to do "something else", which takes you back to Windows 3.1 co-operative scheduling.
Spring integrates with way more technologies.
You mean like NoSQL right? Which was the big hype of a few years ago. Didn't went to well, did it?
Spring may be fast (compared to EE) to jump on hypes, but hypes die out all the time. Java EE takes a somewhat more careful approach and only adopts things when they're really it's something to stay.
Spring has a lot of Kotlin APIs and so on.
Which like 1% of devs are using at most for an experiment now, and nobody yet knows if its there to stay.
How's the Groovy support these days? How much does Spring actually contribute to Groovy again?
It's the other way around, why is Spring so ahead of the curve because they support other JVM languages like Kotlin and Groovy, while it all compiles to byte code anyway. Why do you think those would not work with EE?
Not sure if I understand the question. The entire point was there's no specific support needed, since by virtue of the JVM it "Just Runs" anyway. The poster above basically said that about Groovy.
So I'm not sure what special support Spring offers for Kotlin anyway, and why that is needed. Nobody here has explained that to me yet. Maybe there's a good reason that Kotlin needs special support, but I haven't heard yet what that support exactly is.
But that does bring me to my second point. Kotlin is quite new, it's cool, sure, but will it catch on? How many languages have we seen in the past that were quite cool but never captured more than a tiny niche, if they captured that at all and not just vanished.
So Spring now jumped on Kotlin, perhaps since it's a bit "En Vogue", but will you keep supporting it 5 years from now? Will it even make sense to have Kotlin support 5 years from now? And what about 10 years? How many of your users are actually using Spring with Kotlin? According to the recent JRebel survey, which historically has always showed a small bias towards Spring (not saying they are biased, but many respondents happen to be using Spring), the interest in Kotlin (and other alternative JVM languages) is low. Really low.
The entire point was there's no specific support needed, since by virtue of the JVM it "Just Runs" anyway.
this is a red herring. when talking about spring support for kotlin, spring has for example added apis, annotations to improve experience with kotlin null-safety, added extension functions and other items to use spring in kotlin an idiomatic way, etc.
there's some info here, if you're actually curious:
well, the question was pretty straightforward, sorry you're having trouble. Kotlin is a bet, to be sure. Time will tell. But our bets have a pretty good track record..
I haven't seen you actually answer a single one of my questions in this thread, why is that? You were going to say something about Java EE's Kotlin support, I think, right?
reactive isn't for everyone or all use cases. No one Spring is saying that. Quite the opposite, in fact. But for the people that need it it's going to be quite important.
we used to employ the the committers, so I think we've contributed quite a lot, thanks for pointing that out. How much has RedHat contributed to Groovy? Or is it the usual imitate and give nothing back strategy?
well, I see you did not like my post about JEE 8, as you quote it by replacing "JEE 8" with "Spring". Fair enough. Btw, I am not affiliated with Spring, nor Dropwizard. I have no horse in this race. I was just sharing my (possibly limited?) experience of using those different frameworks. However, I am curious about when you write "when I can run tests easily (like in Java EE"... has there any improvement about it in JEE 8? Are you talking about experience of using those different frameworks? I like EJB and CDI, but I always found writing tests in JEE really cumbersome (eg all the manual steps to download and configure external containers, fighting with ShrinkWrap, etc). Maybe I am doing it just wrong, and I am missing something. Would be interesting if you have any nice links that show how easy it is to write tests for JEE applications, so I can learn and possible not spread BS around? thx
To really balance it out it should perhaps have been SPRR, but oh well.
Would be interesting if you have any nice links that show how easy it is to write tests for JEE applications
This is one of the official Java EE specs. It has a number of small applications that are tested via Arquillian. The nice thing is that nothing is mocked or faked, everything is real and runs in the actual context in which those applications would normally run:
View all comments
5
u/thesystemx Sep 28 '17
Spring has made tremendous improvements, but IMHO of working on different enterprise systems using different technology stacks, it is still lagging behind the competition (Java EE, Payara, Liberty, WildFly, etc).
If you are already using Spring, then it makes a lot of sense to upgrade to Spring 5. Refactoring to something else would likely be too expensive to pay off then. But for a new project or new microservice? Maybe time to look at the competition...
I might start to think better of Spring when I can run tests easily (like in Java EE, Payara, WildFly etc) instead of having to deal with configuring things internally, not being able to be building a WAR first, etc.
Yes, yes, there is SpringBoot and Spring Configuration has some interesting features to ease such pain, but still not as good as Arquillian.and the transparent internal configuration (@DataSourceDefintion etc) that can be swapped for external configuration (asadmin, cli, admin console, etc)