3 ms·
I got a away with the impression that some of those large, enterprise-ey applications are so large and convoluted in the way they are specified that the bloat J
by krylon 10y ago
I got a away with the impression that some of those large, enterprise-ey applications are so large and convoluted in the way they are specified that the bloat Java EE adds appears negligible.
After I had the honor of writing a few simple-minded Perl-CGI-script to give my boss an overview of projects our company is working on and their respective profit margins, I begun to understand why. If somebody tells me computers are complicated, I tell them that computers are trivial compared to accounting. Or my brain is just wired that way... Listening to our accountants always makes me feel like me IQ just dropped by fifty percent (or more). So if somebody writes a piece of software that is somehow involved with accounting, it is bound to be very complex with lots of special cases and exceptions.
I have nothing but the utmost respect for our accountants who manage to deal with this insanity without sacrificing a goat to Cthulhu or something.
TL;DR - once one reaches that level of complexity, the complexity JavaEE puts into the mix is probably fairly tame and one has bigger fish to fry or escape from.
- geodel 10y agoI'd slightly disagree because considering we are discussing impending fall of JavaEE where as enterprises seems as complex as ever. So it would mean JavaEE is not really proved right solution to complex enterprise problems. I feel JavaEE is very large orthogonal complexity which somehow neither solved nor reduced enterprise complexity. It added a jargon speak and multiple layers to bury enterprise problems and reduced net understanding of issues.