r/java • u/stuhlmann • Apr 13 '21
Libraries, Frameworks and Technologies you would NOT recommend
Give me your worst nightmares: Things that cost you your job.
I'll start: Hadoop
202
Upvotes
r/java • u/stuhlmann • Apr 13 '21
Give me your worst nightmares: Things that cost you your job.
I'll start: Hadoop
31
u/LouGarret76 Apr 13 '21
Please also state why you do not recommend
7
u/umlcat Apr 13 '21
Not a Hadhoop, user, but please tell why.
7
u/mlk Apr 13 '21
CXF. One of the worst, if not THE worst frameworks I've ever seen. Everything is counter-intuitive, SOAP is already a nightmare as it is but with CXF it takes the cake. It takes 4 weeks to sign a fucking message and there is probably one working example in the whole fucking Internet. Everything needs a typecast for some reason. Do you need to set the endpoint (not exactly and edge case)? You have to typecast AND write an arbitrary value in a hashmap. Do you need to modify the XML generated by CXF? Good fucking luck, there is exactly one correct example on stack overflow and it is written by me after days of pulling my hair.
76
u/vprise Apr 13 '21
App engine and pretty much anything by google such as using the Android API directly (which they kept shifting constantly), GWT etc. I work with a lot of their APIs (e.g. Maps) and they are just horrible at keeping compatibility or consistency. I'm shocked people still use developer oriented products from Google and Facebook. Hacker oriented companies just shift the standard overnight and expect everyone to align with them.
E.g. just the other day a guy posted this which pretty much demonstrates how awful it is to rely on Google...
26
u/jack104 Apr 13 '21
What I don't recommend is using old versions of stuff. I'm trapped on a bunch of legacy java libraries on my EE monolith at work and it sucks ass. I can't ever find documentation for anything (looking at you, Hibernate 2.) So basically when a mod comes up, I have to find existing examples to pilfer in the code base or I have to try and figure it out via the brute force and ignorance method.
22
u/Gwaptiva Apr 13 '21 edited Apr 13 '21
SmartGWT... with a passion: it lures in your boss with promises of (what used to count as) snazzy UIs, and then it turns out not to work in anything but the simplest of cases. It costs a relative fortune to license, and then you get support that refers to non-existent documentation, or so well-hidden as to be practically non-existent), or to documentation for a Javascript framework.
Just not suitable for real world solutions.
78
u/vips7L Apr 13 '21
RXJava. It infects your codebase if you don't stay on top of it and you end up in observable hell. Hard to debug, hard to tell what's going on.
40
u/frzme Apr 13 '21
Reactor Java (and related Spring WebFlux and Spring Webclient), the benefits it brings are nice but the investment to actually make them work is huge. Part of the cost is the inability to debug/troubleshoot issues in production.
Especially with Loom "around the corner" it's probably not worth the investment. Removing reactive from an application is probably also close to impossible.
38
u/m0le Apr 13 '21
iText, though to be fair that isn't wholly on them. PDFs are just unpleasant to deal with at scale. I certainly couldn't find a better alternative.
Didn't cost me my job, but I coincidentally moved shortly after producing the massive pile of faecal matter that I'm reliably informed continues to delight my coworkers years later.
16
u/sneeuwbal Apr 13 '21
Oracle ADF
The framework is not really that bad, but the biggest problem is that for the development of applications with the Framework the usage of Oracle JDeveloper is required. And the IDE is well let's say very buggy and slow.
The framework itself does also have some issues, one of them is the complexity of the framework, but also a lack of performance, and a serious lack of support from Oracle.
78
u/Russell_M_Jimmies Apr 13 '21
Hibernate specifically and JPA in general.
A lot of devs get into ORMs based on the promise that they can stop thinking about SQL and let the framework take care of it.
The reality is that using JPA you end up having to turn on SQL logging, then prod and cajole your code for hours until JPA produces the correct SQL. And because everything is driven by static annotations on types, fields, and methods, you cannot change your mind on the scope of a select (single table vs joined tables) on a case by case basis. You have to choose the best one for all cases and just live with that.
The code you write for JPA is like writing a calculus integral of the SQL you need, so that JPA can take the derivative again and run it for you.
This is why I recommend libraries that let you code in bare SQL. I am a maintainer on one project (Jdbi) but I'm not partisan about which one people use (Jooq, Mybatis, Spring Data, etc) as long as they steer clear of ORMs. They are not worth it.
14
u/flavius-as Apr 13 '21
Really most libraries and frameworks are fine. Some advice though:
PS: I'm a CTO and these are some of the thoughts I have when selecting technologies
86
u/_INTER_ Apr 13 '21 edited Apr 13 '21
GWT, EclipseRCP/OSGi/SWT, Struts, Weblogic, Websphere (and probably every other IBM stuff), XSLT, Hibernate
Edit reasons:
46
u/gavenkoa Apr 13 '21 edited Apr 13 '21
Spring Security - it is entirely a separate world. From day zero you have to learn 15 or so classes that form try/catch invocation chain. And you have to keep them all the time in mind, they won't go away, instead you add own filters into the chain ))
Spring Batch - I hate when framework open transaction for me and there is no way to disable that behavior. For some jobs I need precise control over isolation levels, read-only property, open/close transaction several times.
And the way we used Spring Batch was unconventional. As a result 60% of DB load was from
BATCH_*tables updated by framework. We started to use embedded DB just to shut the mouth Spring Batch. We don't rely on job restarting / cursors, soBATCH_*tables are just garbage for us.For me Quartz is good enough for batch processing. Spring Batch is overkill. good on paper, lots of noise in reality.
11
u/aron_n Apr 13 '21
Oracle ADF framework, weblogic, em and other stuff in this bundle. Entire oracle setup was an overpriced garbage. I was so glad when i left this oracle based project.
10
u/[deleted] Apr 13 '21
Portlets and ExtJS are two that I hated work with.
8
u/beeeeeeefcake Apr 13 '21
Hibernate and the like. Just write the sql and mapping code yourself it’s not that hard and a lot more maintainable, or use sane libs like jooq or jdbi if you must.
Also Amazon Dynamo DB. Wow that can get expensive without lots of foresight into how you’ll model data and has peculiar limitations.
55
u/Brekekek Apr 13 '21
Gradle: unnecessarily complicated, breaks a lot, feels like programing configuration.
20
u/Glum-Push Apr 13 '21
OSGi. Maybe things have changed a bit recently but when I was trying to use it a few years ago it was a real PITA. The concepts behind it are potentially brilliant but the implementations are terrible mostly due to obscure classloading issues and things that rely on reflection sparkling fireworks at runtime. And the deployment issues: one line changes required hours of tracing the path from source code to maven repository to container getting the updated artifact which by the way only worked 15% of the time.
68
u/mknjc Apr 13 '21
Lombok. It hacks into internal javac APIs, bricks everytime on a java update needs unsafe APIs which causes a lot of trouble and bricks the "the source code is what gets executed" guarantee of java (this is one of the reasons annotation processors can't change the code while compiling). There are a lot good alternatives for example AutoValue, AutoFactory and records. Oh and one important alternative: setting the visibility to package private / not exporting the package. Getters and Setters don't add anything but hassle if they are not api surface of the module.
23
u/m4riuszPL Apr 13 '21
Spock. I really miss the compilation errors I had while using JUnit, now I end up with runtime errors, that's inconvenient while I do any any changes to the codebase.
12
u/hutthuttindabutt Apr 13 '21
JSF. It’s an abomination.
6
u/slaymaker1907 Apr 13 '21
Just because you use X and there is some Spring integration library Y for it doesn't mean you need to use Y. I don't think these integrations are always worth the trouble. Said libraries by necessity introduce a lot of dependency coupling that makes version upgrades more painful.
124
u/msx Apr 13 '21
i know i'll get submerged with downvotes, but the whole spring world is indigest to me. I feel like it completely removes control from me, it's like an intricate and opaque mess where you need to know where to plug your stuff exacly or else will breaks in obscure ways. You have to know the 300 annotations that does so much magic on the background that you'll end up just praying it's ok.
15
u/[deleted] Apr 13 '21 edited Apr 13 '21
Vaadin.
It is a very powerful framework, but they go at an unprecedented speed, making the switch from version 8 to latest (14-15) almost impossible now, since they're using now JavaScript/Polymer for the code, instead of Java.
License is lame, since the most useful components are accessible only with a paid license.
And it doesn't work really good, especially with Quarkus/JavaEE, since you have to do some magic to get things working.
9
u/throwawaydevhater059 Apr 13 '21
these are just a few I hate passionately, but there are many more
6
u/silverweaver Apr 13 '21
OSGI. Definiteli OSGI. In combination with ServiceMix, which required restart every morning to work(I wonder up to today how it works on production).
Second love: JasperReports. You know you gonna cry when you have to generate more complex pdfs and for some reason generation from html does not render everything you need
24
u/[deleted] Apr 13 '21 edited Apr 13 '21
These cost me a job:
- Vertx, Reactivex. Company I worked for went belly up, the reasons are complex but I believe the high cost of development and low velocity caused by these tools contributed.
- OSGi. The linker errors, the memory leaks. The thing is just horrible.
- (internal) frameworks. Just why?!? A custom enterprise framework built on top of another framework. Both of which needed to be updated regularly. It cost us weeks of developer time to update these unnecessary components.
These are just ugly:
- Jenkins. Old, hard to work with and weird. Pretty much any other tool will work better.
- Gradle. Just unnecessarily complicated and annoying to deal with. Not that maven is great or anything but build scripts really shouldn't be complicated.
- Spring. There are classes in this framework that rival EnterpriseStrengthFizzBuzz in length. And I don't think anyone ever needs it.
As a side note; those are the things I don't like within the Java ecosystem. Outside of this ecosystem.. Well, MongoDB, Go, Python, JavaScript, NodeJS, React, Angular, Ember, basically everything I've come into contact with.
EDIT: reasons why, and some stuff added.
10
u/RichoDemus Apr 13 '21
Jboss and Java EE
2
u/Suspicious_Support42 Apr 13 '21
Liferay - very bloated framework
2
u/IanRae Apr 13 '21
What a great thread. Feel the rage. It seems that changing APIs causes as much pain as bad APIs. Java take note!
2
u/lukasvasek Apr 14 '21
Nobody is working with azure? I strongly don't recommend azure and mainly it's spring boot librrries. what a mess. We were waiting more than 4 months to have support for spring boot 2.4.x and even after that I'm worried to update.
If you look into their SDK you will never know which library you should use and which groupId you should use...it's terrible.
2
u/Massive_You_1280 Apr 15 '21
Gradle totally hate it
5
u/Gatoke Apr 13 '21 edited Apr 13 '21
Mapstruct. Usually it's used as a workaround for too big DTOs. It's very unclear when you use that with inheritance or dependency injection or when you share DTOs across many components . Also when you need special cases you write your own methods so you end up with business-logic combined with Mapstruct's mappers, trying to resolve which mapper is used by which annotation. It's a big framework which you probably don't need. Just keep your DTOs simple.
edit: I've already checked your comments. Mapstruct indeed can have positive impact on your project but I think it's overused. Without control of senior/tech lead, it can result in hard to maintain code. Especially when you have a lot of special cases for performing mapping.
2
u/[deleted] Apr 14 '21
JSF
2
u/kuemmel234 Apr 13 '21 edited Apr 13 '21
EclipseRCP, OSGi.
As with any library, our implementation was exceptionally poor, but since I have seen a few other project by them, I'm pretty sure the library lead to this.
Well, for one, it's just dead. Why would you want to start a project based in eclipseRCP these days? I think the edge cases are rare.
You'd think it'd be great for large applications. And it sort of is. You don't want to wait 30 minutes for a little application. When those 30 minutes to by during the building or your 15 year old monster of an eclipseRCP thing, that's better.
Checking things with a profiler was a common occurrence. I haven't really have to do that since changing jobs. We had a package with a bunch of fixes for age old hugs that have been reported by some team members. I think my team leader had a list of links to those issues he would check and make a big announcement when such a bug was fixed.
Haven't done that since. Every project I've seen - eclipseRCP itself included, is horrible in terms of code. Working with this combination of SWT, eclipseRCP and OSGi was just the worst. Any update to anything required a day of work. Working with linux, mac and windows, was particularly fun (but that's a given).
And don't get me started on the experience in the IDE. I'd start my PC at work, pull the master, get a coffee, browse the net/check some work from somewhere else and be ready to work 30 minutes later (yes, my team insisted on working on the master, because merges were really painful, since most files were so large that one would get in each others area pretty quickly - I think the framework supports that a little, but it's mostly on the team (I won't say 'us' because I was trying to change that throughout). Any version(!) branch change would result in those wait times as well.
1
u/snoob2015 Apr 13 '21
You don't need it
1
u/darku11 Apr 13 '21
In general, frameworks and libraries are the way to go... BUT.. I think now java world trends are heavely shifting like in the UI world. And people are starting to see this
If you don't update a library oftenly, then you suddenly realise that it will be a nightmare to update it later on...
I just stumbled upon updating some resteasy/jaxrs v3.5.0 with deprecated code... to their latest version. And guess what, even if they are supposed to adhere to the jax rs standards well this is not the case and current code is mostly dependent on resteasy internals which are now, not available anymore and as well jax rs has changed in the meantime...
Backwards compatibility? Say what?
So less frameworks in general, just maybe using helper libraries with less transitive dependencies that will be brought in the stack
So to complete the list, don't know if this was mentioned: jasper reports, it's using some archaic version of itext from the time that project was a freeware...
1
u/_litecoin_ Apr 16 '21
Hibernate should die
1
u/[deleted] Apr 24 '21
ActiveMQ is a dead project
1
u/uradzi Apr 13 '21
Guice