4 ms·
I've read this before and it's an excellent diatribe. However, it's as much of a knock against Java's limitations as it is against frameworks in general. Framew
by InclinedPlane 16y ago
I've read this before and it's an excellent diatribe. However, it's as much of a knock against Java's limitations as it is against frameworks in general. Frameworks in other languages are not nearly so onerous or convoluted.
- forinti 16y agoI don't understand why this culture of making things ever more complicated has grown up around Java. I've given up using these trendy frameworks and make do with just Struts/Tiles and plain JSPs. I've recently rewritten an application that used Oracle ADF and it came out 10% the size of the original. What I've found is that many IT departments feel pressured to use Java but don't really want to learn Java, so they try to find an IDE that will let them build the GUI without coding and a framework that will turn most of the job into configuration through XML. The result is that the solutions are a lot more complex and people hate Java.
- superuser2 16y agoBut.. but... but... we're an Enterprise! Any language that doesn't require writing a Dao and a DaoImpl and a Service and a ServiceImpl and a Controller and a ControllerImpl and an extremely verbose JSP template and about a hundred lines of XML to do something trivial is a toy! I don't care if YouTube scales to hundreds of millions of users with Python, our 200-user website is mission-critical and demands scalability!
- boyter 16y agoThe above comment describes everything I work with on a day to day basis at my job. Every solution contains multiple layers of abstraction from the aspx to the code behind, to a controller to multiple services to multiple daos and with all of them implementing something to allow for testing. Except very little is tested (its getting better) and everything is so tightly coupled it dosnt make a difference anyway.
- arethuza 16y agoI once had to try and salvage something useful from a huge J2EE application where the development team were obviously as they say "taking the p*ss". At one point I counted 23 layers of abstraction between the fairly simple JSP page through EJBs and a connector to eventually make a simple SOAP call to get the data to go on the page. Everyone of those layers had an interface, a factory and an implementation....
- arethuza 16y agoSome of the source code was missing too - so I had to decompile great chunks of stuff and wade through the resulting code to find out what was going on. Imagine my delight when I found multiple jar files, all with the same name but with different contents, all included in the classpath for WebSphere. Something like 98% of the code did nothing useful.
- wazoox 16y ago> I don't understand why this culture of making things ever more complicated has grown up around Java. Because nothing is more enterprisey than "architecture astronautics". Also, it's a nice way to spend time doing nothing useful in a large bureaucracy.
- InclinedPlane 16y agoJava is a fine language, but it has some significant limits. Unfortunately Java has become the de facto general purpose language in many places, especially in "the enterprise". So a lot of tools have been built in and on top of Java which allow you to do anything and everything with it, even when other languages would be a far more natural fit and would require drastically less development effort. Worse yet, many dyed-in-the-wool javaists also have mental blinkers (see: blub language) which prevents them from seeing outside the limits of the language, leading them to believe that it's perfectly natural and normal for an MVC application to require mountains of code, mountains of XML, and every detail reproduced in exacting triplicate across the depth of the framework. Simply because they lack the perspective to realize that they're missing out.
- aerique 16y agoI don't understand why this culture of making things ever more complicated has grown up around Java. I think it is because of the whole corporate ecosystem that surrounds it. There's experts that need to make a name for themselves, consultants that need to make money, companies that need to sell services or consultants, etc. etc.
- coliveira 16y agoWhat about the fact that everything needs to be a class? This works on Javascript or Smalltalk, which are dynamic languages, but not in a static language. There is no way to have a function callback mechanism without introducing new classes. The very culture of using design patterns for everything is just a reflection on how things are solved in Java.
- axod 16y agoIt's not Java the language that is the issue here, it's just the way it's used in corporate land.
- jackfoxy 16y agoThe experience at our company with .NET kind of illustrates the subtle differences between "frameworks" and "collections of libraries". Microsoft bills .NET as a framework, but from a practical perspective it's really a big collection of libraries (and languages) which is great. ASP.NET, and to a lesser extent ADO.NET, although theoretically sub-collections of libraries, are really more like frameworks. And while some of their features are nice (e.g. forms authentication), you recognize the maze of factories building factories when something cleaner (like jQuery) comes along. Frameworks can be like training wheels. They can help you get started and keep you going, but as you get more sophisticated you realize they are in the way.
- DougWebb 16y agoI'm curious to hear your opinion of SharePoint, if you have one. I'm new to the C# world and I'm pleasantly surprised that it's not as bad as Java like I thought it would be, but I've mostly been focused on the language and core libraries. I think I like it for the reason you describe: it's libraries, rather than frameworks. But I've started getting into some ASP.NET code and the frameworkiness is starting to appear. In my case it's entity objects which don't seem to do more than structs, interfaces for classes which talk to the entity objects, implementation classes to implement the interfaces which just copy data from entity objects into their own properties, business objects which talk to the interfaces to get to the entity data, and UI objects/templates that talk to the business objects, probably through another layer of interface/implementation. From what I can tell, SharePoint is another big layer of framework on top of ASP.NET, governing the way your application must be designed and function.
- sgift 16y agoIt is another big layer of framework on top of ASP.NET which does _not_ work reliably. Be prepared to spend your time producing bugfixes for subtle and/or obscure bugs which you will have on one sharepoint installation but not on another. Install sharepoint twice on different systems and there will be differences right after the installation. I program at the moment c# and java for a living and c# is fine (java too, if you can ignore all the frameworks). But sharepoint is a PITA. Don't get me started on complex webparts, getting them to work is weird - if there's a programmers hell I'm pretty sure you will have to program for sharepoint there. (note: All information for sharepoint 2007)