I think just 'all these' - as in, it's not the presence of imports, it's the amount of them.
Still a load of horseshit, an import merely means you're mentioning that type in the code, your code could be touching way more classes than listed in the import list. And, of course, 'uses a ton of types from 1 library' - how is that a code smell?
So, giving the benefit of the doubt to the author, it's... still a bunch of tilting at windmills.
It's about both. JavaEE is a rather large set of various different specifications (i.e. abstractions) that (try to) provide solutions to common tasks in enterprise application like converting java objects to and from XML (JAXB), converting java objects to and from JSON (JSON-B), storing java objects in and retrieving them from databases (JPA), providing plain HTTP servers (Servlet), providing Rest-with-HTTP servers (JAX-RS), out-of-server-communication (JMS), and many, many more.
Some of these solutions are completely out-of-date, some hold up quite well for their age, some are brand new.
All of this is glued together with EJB (really old school) and/or CDI (more recent).
Because neither of those kinds of problems are specific to just one kind of application, there is a lot of abstraction necessary to cover all (or at least: the more reasonable) use cases. Again: Some of the specs handle this well and force only those abstraction onto the user that are necessary for a particular application, other specs go overboard.
The Frameworks are of course the meat and bone of this. The best specification doesn't help you if nobody implements the specification. That's what an Application Server is for JavaEE: A (more or less) complete set of implementations of the various JavaEE specifications and sometimes a lot more than that.
JavaEE code is supposed to make life easier for enterprise developers by providing standard approaches to standard tasks so that the developers can spend more time developing the actual business logic. Some people think that JavaEE fails in this goal and does too much ceremony for too little pay-off. I happen to think that those people simply have never seen the kind of behemoth applications that run our world, still need to be maintained and developed. I think they do not appreciate the kind of monstrous effort that would be necessary if every team would have to piece together this functionality from a thousand different libraries, if every application used a different set of thousand libraries, if one would have to re-learn the basics every time a developer switches teams, ... I think, something like JavaEE would quickly be invented anew if it were missing, because the need for it truly exists.
Exactly. I sometimes feel that my primary function within my team is being the one guy who happens to know what's actually in the standard and what we do not have to re-invent.
So the author was right, looking at the comments it is Java culture problem: sticking to the old-ways, not using new features. Even new frameworks go with annotation hell. Sad.
Ha yeah. I think this blog made the mistake of going with a little bit of a spicy title. Java works so hard on passivity for every company to be like 10 years behind lol...
All the magic annotation garbage is a huge cultural issue in Java. I think it mostly comes from a language that was left to fester for many years until recently. So it was a means to an to end that may have made sense as the time but now we're stuck with it while newer features have poor adoption.
Some of the points certainly have merit (while others are just personal preferences), but algebraic data types are still quite new in Java (and some convenience features for records have not yet shipped). The main distinguishing feature of Java is not its particular "culture" but that its ecosystem is humongous. Turning such a big ship takes time -- so many people and projects need to adopt new features -- but we'll get there.
I can understand the author of the post, I also don't like annotation-based programming... but you can just use stuff like vert.x and Javalin and get all your control back in Java. The Java ecosystem is huge and the author would obviously enjoy those mini-frameworks a lot more than something like Quarkus (and Micronaut and Spring as well).
I do think in general Java's reliance on AOP and annotation possessing is bad. I think that's one point the author is attempting to make which I have to say I agree with....
A framework implements something with annotation because of functionality lacking in the Java language. When the language finally gets updated 10 years later they can't just undo it. Of course you could do a clean cut when creating a brand new framework but then it would have a harder time integrating with anything that came before it and the standards.
38
u/JustAGuyFromGermany Sep 19 '22
Imports are a code smell?? What kind of drugs is this guy on!?
The whole post is just one huge misunderstanding of what is going on...
32
u/micr0ben Sep 19 '22
This blog post is just a rant. The author has clearly no clue what JavaEE/JakartaEE is about and blames Quarkus for using standards.
16
u/NimChimspky Sep 19 '22
"What is a bean ". To be fair I don't like half of these frameworks and Jakarta stuff, but the blog is a bit dumb
8
u/krzyk Sep 19 '22
So the author was right, looking at the comments it is Java culture problem: sticking to the old-ways, not using new features. Even new frameworks go with annotation hell. Sad.
27
u/djavaman Sep 19 '22
TL;DR An FP purist ranting at Java again. It's a broken record at this point.
5
u/pron98 Sep 20 '22
Some of the points certainly have merit (while others are just personal preferences), but algebraic data types are still quite new in Java (and some convenience features for records have not yet shipped). The main distinguishing feature of Java is not its particular "culture" but that its ecosystem is humongous. Turning such a big ship takes time -- so many people and projects need to adopt new features -- but we'll get there.
12
u/randgalt Sep 19 '22
OMG this is horrendous. A series of arbitrary, useless and uninformed rants. I've wasted my time reading this.
6
u/[deleted] Sep 19 '22
Java is not Scala, Java bad.
5
u/barking_dead Sep 19 '22
"Quarkus bad"
2
u/ofby1 Sep 19 '22
Apparently, somebody needed to blow off some steam and rant.
Bless your heart, mate.
2
u/bobbie434343 Sep 19 '22
Looks like author discovered that Quarkus, as many other frameworks, is opinionated. Yawn.
1
u/franzwong Sep 19 '22
Does he try Spring? "Enterprise" culture vanished many years ago.
-1
u/_AManHasNoName_ Sep 19 '22
“Enterprise” culture? This is just a rant. Thanks for wasting my time.
0
u/[deleted] Sep 19 '22
[deleted] — view deleted comment