101–107 of 107 posts
Earlier quoted context omitted.
What's the big deal with setting up a "JVM Environment"? Working with Scala for me involves the latest Scala distro and a copy of VIM. Is there something in particular that makes it so painful that I"m missing?
Yes--there's more to setting up a JEE stack then getting a JVM and a language running.
I am a Java developer in my day to day work but I'll give a few reasons: 1. The memory footprint of the JVM is significantly larger for a similar app vs. PHP. Also, it requires a lot of tricky JVM option tweaking to get it to work in anything less than about 512mb. 2. The build environment is really heavy weight and complicated. Maven seemed crazy at first though working with it for a while finally got me used to it.…
2. It doesn't have to be complicated - it's the developers who make it so.
3. it depends on your server and configuration. Every server supports class reloading and jsp recompiling.
4. You don't have to - eclipse and netbeans are free and very powerful. Notepad for simple tweaks if you have to.
Just to set up one of the Java frameworks you list is already a lot of work and a lot of wrangling of XML. Without frameworks, it is probably OK if you already have a working web.xml. I used to just copy my working web.xml and modify it. Good luck if you want to create a working web.xml from scratch, though. The specification for a proper web.xml is a PDF with several 100 pages (last time I looked, a couple of years…
This is one of the specific reasons the Stripes Framework ( http://stripesframework.org/display/stripes/Home ) was created. The idea behind it is that most Java frameworks require too much configuration and the start-up time (to get rolling with development) isn't short. Stripes looks to solve both of these problems while making it (actually) fun to do Java development. There's extremely little XML config setup. Ther…
IMHO the answer is here in this thread... which would you choose? a) php b) rails c) Java + JSP/Servlets/JSTL/Tiles/Struts/Spring/JSF/Play/Wicket/GWT/Stripes/Tapestry/WebObjects
This is not really accurate. When using java, you will not use JSP, JSTL, JSF, Play, Wicket, STripes, Tapestry, etc, all at the same time . Unless you are crazy. The same way, in Ruby, you will not use ERB, Haml, Erector, Markaby, or the other (at least) 19 template engines out there ( http://www.hokstad.com/mini-reviews-of-19-ruby-template-engi... ) But this comparison is not actually fair, because you mixxed templa…
It takes you 10 periods of time in JSP to do what you can do in PHP in 1 period of time.
-steep learning curve compared to rails, django, grails, etc - lots of configuration (I mean a lot, no convention over configuration) - application servers are not easy, tomcat can be a nightmare in term of rapid deployment/undeploy routines, just think about heroku on the other hand
Earlier quoted context omitted.
- I can't stand working in an IDE. Are you saying this because you mostly work with smaller web apps, or other reasons? For larger projects I find IDE's (especially Eclipse for JAVA indispensable).
I work mostly on large web apps but that doesn't have much to do with my dislike for IDE's. The reason I don't like them is that I don't want 90% of what it gives me. My 'IDE' is 1 gvim per project and a terminal app with a couple tabs. I can't think of anything an IDE gives me that I don't a) want or b) already have.