Struts 1.1 Released
Evil Grinn writes "The long-awaited release of Struts 1.1 has finally happened. See the release notes for all of the changes since the last Release Candidate and also since Struts 1.0.2. Many new features are available in a stable production release for the first time today. Congratulations to the entire Struts team."
It took them long enough to decide to finally release a final version! :-P
I'm not complaining. It's great that they did - now finally all those IDE vendors are going to put real struts 1.1 support in their software. It's a very good step politically and for the general acceptation of Struts by corporations and such.
Daniel
Carpe Diem
Struts is a web application development framework (WADF), of which there are many.
While factually correct, "many" might be an understatement. It seems everyone and their uncle/brother/dog/etc. are inventing WADFs, which get haphazardly adopted by organizations throughout the world leaving web developers feeling their resume is somehow inadeqate.
Some of them seem to prefer WebWork, which is now part of OpenSymphony. Debate over Struts is raging.
This is what is so frustrating, where the turn-over in fashionable WADFs is rampant. I would cringe upon hearing "Struts is so, like, 2001." That was only two years ago! Ugh.
Rather than adopting a "framework" that is almost certain to fall short in its capacity, why don't web developers adopt something even better: objective simplicity. Frameworks can be a constant battling ground for new employees and old employees alike, when learning and re-learning the framework becomes burdensome. Isn't good software architecture supposed to make things intuitive, even to the average software developer?
I believe the multitude of frameworks are the product of severe NIH syndrome, rather than genuine well-intentioned common sense.
Healthcare article at Kuro5hin
Wish I had points with which to mod you up.
However, I do have a couple of minor observations. Objective simplicity is a laudable goal, but it conflicts with the goals of flexibility, performance, and ability to meet the requirements of the subject matter (if the subject matter is complex). There are always tradeoffs to be made.
And, it could be argued that a profusion of WADF's is a good thing in that it puts a wide variety of ideas out there, which should (in theory) yield a higher chance of something good showing up.
Yours are still valid concerns though.
Read my keyboard review.
A few months ago, Jakarta started to host several projects that do the same thing
(torque ojb, ant maven, etc). The same happens with strutus turbine.
I have written some applications using turbine, and like the framework. The thing is, if "now finally all those IDE vendors are going to put real struts 1.1 support in their software" they will probably not do this for tubine. Should I give up on turbine?