5 ms·
I may work with java soon, so I was reading about Spring and it was yet again a dive into insane amount of verbose over engineering that I ran away from years a
by agumonkey 7y ago
I may work with java soon, so I was reading about Spring and it was yet again a dive into insane amount of verbose over engineering that I ran away from years ago.
It's true that post 8 Java becomes palatable. And someone on reddit just showed me this piece of stats:
https://www.jetbrains.com/lp/devecosystem-2019/java/ https://www.jetbrains.com/lp/devecosystem-2019/java/
83% on java 8, java 11 nicely going up
I pity those forced to work with old techniques
- maltalex 7y agoI write quite a lot of Java, and I have to admit I never “got” Spring. I’d much rather have explicit boilerplate code (preferably in library form as much as possible) than complex, invisible magic. The latter is “easy”, but the former is “simple”. In most cases, “simple” is more important.
- unscaled 7y agoBut Spring gives you the best of both worlds. A lot of verbose code (as annotations and class inflation instead of explicit boilerplate) and inscrutable magic.
- arethuza 7y agoIf only we could all agree on what "simple" means - a lot of "enterprise" code I've seen would sweep vast amounts of complexity into hard to spot places to that you could have a small thing that people could point at and say how simple the one visible bit was, ignoring the vast amount of complexity lurking under the surface somewhere and invoked by more or less magical means.
- nurettin 7y agoI'd say there is no upside for the complex invisible magic. Half the time you have to run the application and pray that the configuration beans you've placed are working and if not, you are pretty much in trouble. Perhaps you missed a step in adding a configuration decorator in your application or configuration class, or used some deprecated method or used some incorrect class in the class hierarchy for the bean you want to return.
- agumonkey 7y agoit's not even magic, it's redundant over engineering at its peak haskell has magic, but at least its concise..
- rhinoceraptor 7y agoIt's like playing Where's Waldo, to find the actual code in an enterprise Java/C# application. I think it's a fundamentally different mentality as far as the code. The codebase is so obfuscated that it might as well be binary data rather than plaintext files. You need an IDE to manipulate it efficiently.
- agumonkey 7y agoI feel like Enterprise is all about looking complex to justify the fees. The simpler it looks the harder it is to bill. http://jeffacubed.com/the-boilermaker-story-or-knowing-where-to-tap/ http://jeffacubed.com/the-boilermaker-story-or-knowing-where...
- oweiler 7y agoI disagree. The "boilerplate" is the boring stuff I don't want to waste my time with.
- maltalex 7y agoIn my opinion software development is less about what specific developers want to spend their time on, and more about producing solid software. Does not spending time on boilerplate improve the quality of software you produce? I find that it doesn't.
- LoSboccacc 7y ago> I pity those forced to work with old techniques java modules broke a lot of software that were using sun classes or did classloading magic. I was on one of such application, it's not a lot of effort to migrate forward, but many of the issues are runtime only so unless you have a good test suite, a strong incentive and no closed source library that use some such classes you can't really move forward with it. anyway, in java 7 was already possible to write "unbloated" code, especially with the servlet 3.0+ spec, but spring and osgi have a lot of inertia in the enterprise community, meaning most people were stuck programming in xml, one of the most unpleasant experience ever.
- agumonkey 7y agoI wonder how much salary increase it would take to make working with xml/spring worth someone's while. ps: also how many shops are doing 'migration off of spring' ?
- mindcrime 7y agoI wonder how much salary increase it would take to make working with xml/spring worth someone's while. Meh.. in my opinion a lot of this is just tropes. Spring is a fine environment to work in, although you really don't have to use any XML with modern Spring. But you can if you prefer to for some reason. All the annotation driven "black magic" can be mildly annoying at times, especially before you understand what's going on under the hood... but considering the amount of boiler-plate crap it saves you from dealing with, I'll happily accept that tradeoff. For my money, if I was starting a new backend service today, I'd absolutely reach for Spring Boot as my starting point. Of course, I may be biased given that I've been writing Java code for 20 years, and I remember what a breath of fresh air Spring was compared to the old EJB 2.x era "J2EE" stuff.
- LoSboccacc 7y ago> old EJB 2.x era "J2EE" could have had worse you started just around the xdoclet, that was peak madness
- foxyv 7y agoI accept your pity. All my code has to be JRE5 compatible...
- agumonkey 7y agoNice constraint.. is it allowed to produce libs in jars from non java languages ? Even though I don't think clojure/kotlin/else support jre5 out of the box anymore.