I prefer scripting languages over a pure Java stack simply because I can reload the page and see what's happening with the new code. Yes, you can use JRebel, hook up a debugger and tweak settings to get some hot code replacement, but they've always failed me at one point or another, resulting in hours of fun. The compile-check-fix-compile cycle gets under my skin, especially when you're using frameworks and libraries…
Ask HN: Why are there so few apps being built with JSP?
21–30 of 107 posts
Re: Ask HN: Why are there so few apps being built with JSP?
#22Just 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…
Managing that stuff should be left the IDE, that's the sort of thing that XML was originally meant for, at least.
Re: Ask HN: Why are there so few apps being built with JSP?
#23Re: Ask HN: Why are there so few apps being built with JSP?
#24Re: Ask HN: Why are there so few apps being built with JSP?
#25Re: Ask HN: Why are there so few apps being built with JSP?
#26I prefer scripting languages over a pure Java stack simply because I can reload the page and see what's happening with the new code. Yes, you can use JRebel, hook up a debugger and tweak settings to get some hot code replacement, but they've always failed me at one point or another, resulting in hours of fun. The compile-check-fix-compile cycle gets under my skin, especially when you're using frameworks and libraries…
Re: Ask HN: Why are there so few apps being built with JSP?
#27a) php b) rails c) Java + JSP/Servlets/JSTL/Tiles/Struts/Spring/JSF/Play/Wicket/GWT/Stripes/Tapestry/WebObjects
Re: Ask HN: Why are there so few apps being built with JSP?
#28On the low end, I've always thought java has a significant disadvantage: memory footprint. In particular, this is compared to PHP/Perl/RoR/etc. When you start your java app you pre-allocate all the memory you're going to need for the process' lifetime. This could be 512MB, this could be 2GB+, but it's never small. And this is unaffected by your initial traffic volume. It's the same for 0.001 hits/sec or 5 hits/sec. O…
Actually I am afraid to host a RoR app on my server, which runs several Java apps. I think the server has only 256MB of RAM (it is old, but cheap), or maybe 512 - not a lot, in any case. I am much more worried about memory consumption of RoR. Never really launched it in production, but wasn't it the case that you have to load balance between several Mongrels, each consuming > 100MB of RAM? Java is just unpleasant to…
Re: Ask HN: Why are there so few apps being built with JSP?
#29I prefer scripting languages over a pure Java stack simply because I can reload the page and see what's happening with the new code. Yes, you can use JRebel, hook up a debugger and tweak settings to get some hot code replacement, but they've always failed me at one point or another, resulting in hours of fun. The compile-check-fix-compile cycle gets under my skin, especially when you're using frameworks and libraries…
Yes, but the question was about jsp, which doesn't require any fancy tricks. :-)
Re: Ask HN: Why are there so few apps being built with JSP?
#30Earlier quoted context omitted.
Yes, but the question was about jsp, which doesn't require any fancy tricks. :-)
Once upon a time some guy thought it would be a great idea to simply construct SQL queries, make the DB calls and loop over the result sets trying to create somewhat decent output, all in a single JSP. I'm so incredibly happy I never had to work with him again. When you're writing a very simple todo list: be my guest. When you're attempting to create any kind of decent application and do use JSPs like this: you're st…