The Debate is flawed: Struts vs. WebWork
Personally, I think the debate between Struts and WebWork is irrelevant. This is because I don't think that the Web Application frameworks are the problem. I spend most of my days getting persistence to work. Granted it's gotten a whole lot easier with Hibernate, but I've spent a lot of time tackling that learning curve in the last couple of months. Thanks to Dave Johnson and Gavin King for guiding me up the curve. I spend about 30 minutes each day writing Struts-related code, if that. More time is spent writing tests, CSS, JavaScript (the most time) and DAO's/Managers.
So the problem is my brain. If I could just get the damn thing to work right - it wouldn't matter which framework I chose, because I'd just know it. No learning curve == awesome productivity.
The WebWork guys claim to have this. Therefore, I'm interested. However, who's hiring WebWork gurus? Heh - I know - what I really need to do is learn WebWork and then I can offer an unbiased opinion. Right now, no one is offering an unbiased opinion. Patrick is heavily invested in Struts, as am I. Heck, I've written a chapter about it and I've used it on many project. Jason is invested in WebWork as he's a committer.
Baaah, I'm just gonna learn .NET - that's where the Florida Jobs are. Struts .NET and WebWork .NET - maybe I should work on getting those started. ;-) The post is meant to be read with a smile on your face - I don't want to start yet another flame war.
Posted by dsuspense on March 04, 2003 at 02:18 AM MST #
Posted by Ian Pojman on October 01, 2003 at 07:11 PM MDT #