4 ms·
This is pretty much why I switched my career from Java development to Ruby and Rails. Java is a fine language and I still enjoy programming in it. The problem
by mberning 16y ago
This is pretty much why I switched my career from Java development to Ruby and Rails.
Java is a fine language and I still enjoy programming in it. The problem is that a large portion of the professional community is very obsessed with these huge frameworks, libraries, and convoluted design patterns. I often faced a lot of opposition trying to simplify our Java platform at my previous job. In the end we were able to completely replace jboss with a simple tomcat instance, which is vastly simpler and much quicker/easier to develop with.
- jarin 16y agoJust the word "factory" sends chills down my spine. I think it may have even influenced my decision to use Machinist instead of factory_girl as my fixture replacement in Rails.
- jbooth 16y agoRails has a lot of the same frameworkiness. If you're writing a big webapp, Ruby's a more appropriate language (Integer.parseInt(request.getParameter("id")) isn't exactly beautiful), but Rails is just as much a framework as SEAM is, up to and including the sort of problem the author complains about. It's just a better one for many applications.
- mberning 16y agoI agree, but I find rails to be very pragmatic. Of course it's no silver bullet, but for many of the projects I've worked on in the past it was a good fit. I feel like it is pretty low friction and has a moderate learning curve as compared with more 'enterprise' frameworks.
- jbooth 16y agoYeah, for sure, I've done very little Rails so I'm not speaking from experience but it seemed that for the variety of problem the author was facing (have to solve a problem "the framework way" for something that should be simple), rails is susceptible as well -- it's just a better set of design choices for the web so it doesn't fall down as often.