4 ms·
"Towering" implies unweidly or disorganized to me and there are certainly parts of the Java world like that -- to be avoided. The number of abstractions/librar
by timf 18y ago
"Towering" implies unweidly or disorganized to me and there are certainly parts of the Java world like that -- to be avoided.
The number of abstractions/libraries seems irrelevant to the discussion if they can indeed be out of your way (you're saying because of all the boilerplate etc. that they aren't, so I guess we're talking about different things). If they're powerful and there's a small surface error for dealing with them then great, that's a high return on investment situation.
Getting to that small surface error takes an IDE sometimes which is unfortunate on some level but I don't find anything fundamentally wrong with it.
Personally, I can't stand even simple programs in Java with a text editor because of the amount of subdirectories you need to suddenly be aware of... org/blah/blah/blah/blah/blah (this is how I learned it originally).
- moe 18y agoWell, it's been a while since I left the java world. Back then it was all about "inverse of control", Spring and the ilk, and maven was starting out. People were basically competing about who can move the most code from java files to xml descriptors and who had the smartest pom.xml... Maybe things have bettered since then but from what I see at least the maven disease seems to still be all over the place. I'm not saying that all these things are necessarily bad. I just grew really tired of juggling monstrous xml blobs around while still being forced to write (or generate) metric tons of boilerplate code.