With Struts 2 I've got testability right down the spine of the application. There's very little Java I can write that I can't test. And testing really does speed up your application development cycle, as I'm sure the pros here know.
The stuff I can't test is what slows me down: JSP, and the gap between my JSP and my Struts actions. There are times where I've screwed up the wiring between them, and can't for the life of me figure out why. I don't have a JSP debugger, and JSPs don't generate log statements (wow, wouldn't it be awesome if they could?). So tracking that down is time-consuming for me. CSS doesn't slow me down nearly as much as it used to thanks to Firebug. Honestly, otherwise, right now I'm working on converting an old ColdFusion app to Struts 2 and the most time-consuming part is figuring out what the hell the previous CF programmer wanted when he wrote his code. jk On Fri, Jun 20, 2008 at 7:43 AM, Ted Husted <[EMAIL PROTECTED]> wrote: > Since it's friday, let me pose a question to the group ... > > Even with rock-solid frameworks like Apache Struts, it still seems > like web application development takes longer than it should. Some > frameworks, like Ruby on Rails, speak directly to "time to market" > concerns and have been gathering many followers. > > But why does web application still seem so difficult or so > time-consuming? Are there time bandits that still suck days or weeks > out of your development schedule? Are there time gremlins that > "nickel-and-dime" you every hour of every day? Is there anything more > that frameworks like Apache Struts can do to help? Or are just there > intractable problems with web development itself? > > Thoughts? :) > > -Ted. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jim Kiley Technical Consultant | Summa [p] 412.258.3346 [m] 412.445.1729 http://www.summa-tech.com
