2 ms·
> It felt slow, heavy, bloated, unnecessarily Enterprise. You can avoid the "unnecessarily Enterprise" by not writing code in the Enterprise fashion. Not eve
by Sohcahtoa82 8y ago
> It felt slow, heavy, bloated, unnecessarily Enterprise.
You can avoid the "unnecessarily Enterprise" by not writing code in the Enterprise fashion.
Not every class needs to be an extension of an abstract class that implements an interface. Not every class needs a factory class. Not every operation needs to be abstracted. If you have a class that has just a constructor and a single function, you probably don't need a class and can just write a function.
Most complaints about Java are really complaints about some idiotic Java paradigms that seem to have been invented by someone that measures productivity in LoC written or classes implemented.
- bayindirh 8y agoJava's "unnecessarily enterprise" feeling didn't come from the paradigms that increase the LoC (abstraction, interfaces, factory classes, etc.), but from the way it developed, where it used and how it behaved. This feeling is also reinforced by the prime editors of that time: Eclipse and Netbeans. Both are behemoths which were written in Java, heavy, resource intensive and somewhat slow. In the 2000s, Java wasn't that fast and refined, and it showed and felt profoundly, at least by me. With the open sourcing of Java and the performance jump happened with Intel's Core i series CPUs, Java got a lot lighter. I've never had hard feelings against any programming language, and I hold no grudge against Java, but I currently don't need it, so I'm not using it.