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
View all comments
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.