by Anonymous Coward writes:
on Friday March 10, 2017 @07:58AM (#54011647)
Whoever chose struts 2 back then probably deserve it
Maybe not for the 6 months in which it was relevant, but for the 13[1] years where all java sweatshops kept on using that piece of shit yes, they deserve it.
I looked at struts2 back in my enterprise java days. There was way too much automagic driven by rails envy where it was doing very dynamic things magically based on the request. Lots of stuff where the request would become a very complex java object that would interact with automagic libraries to do dangerous things and you just had to trust their weren't any exploits. I decided to use json servlets and single page web app frameworks instead.
As long as it is clearly documented what it will do, and you know what precisely what it will having it automatically do things isnt necessarily bad, can save time, as long as finer grain control is allowed. If it is poorly documented and does unexpected things, this is pretty bad. Allowing a system command to be run is a pretty nasty undocumented automatic behaviour.
Whoever chose struts 2 back then probably deserve it
Maybe not for the 6 months in which it was relevant, but for the 13[1] years where all java sweatshops kept on using that piece of shit yes, they deserve it.
[1]not a precise number
Struts 2 is fine. It works fine. It with JSP/JSTL is all you ever need in the general case. Everything else is sugar (except few problem domains where you truly need something new.) I like Vaadim and Stripes, but I've seen enough sites VERY WELL built with plain old Struts and JPS/JSTL to know it is the wielder, not the tool.)
If you have a decently built system that runs well on Struts, why change it? Just to try something new? That's not engineering, that's playing on someone else's dime.
Struts was the only thing available for a long time back in the dark ages of J2EE. So a lot of smart people were drawn into doing stupid things because that was the only thing available.
By the time Struts 2 came about it was about the time most smart people realised how stupid the whole J2EE thing was and abandoned it and starting trying out better things. Most stupid people went on to Struts 2.
Struts was the only thing available for a long time back in the dark ages of J2EE. So a lot of smart people were drawn into doing stupid things because that was the only thing available.
By the time Struts 2 came about it was about the time most smart people realised how stupid the whole J2EE thing was and abandoned it and starting trying out better things. Most stupid people went on to Struts 2.
That's an axiomatic, self-fulfilling statement. Congratulations.
dude.... you are confusing Struts and Struts 2. They have nothing in common but the name.
No, I just never cared to call them Struts and Struts 2. Both are fine, having worked on them both. I can see why why my lazy wording would confuse people, though.
Vaadin wasn't known as Vaadin back then and really was not that popular until post 2009 or even later.
And no Millstone and IT Mills toolkit (Vaadin's old name) are not serious contenders when Struts 2 came out.
Considering Struts 2 came out with lots of hype and went out of favour very very quickly, I would say the peak of Struts 2 hype did not overlap with when Vaadin started getting popular.
Ok... unless you are talking about really really really stupid people who still chose Struts 2 after 2010. I think it
Back then even staying on struts 1 was smarter than going with struts 2 which is a completely different framework and not a version upgrade.
People blindly jumped on Struts 2 because there was a time where everyone used Struts 1. Because.... hey who would want to have an iPhone 6 when an iPhone 7 is already out? It's so passe!
"When the only tool you have is a hammer, you tend to treat everything as if
it were a nail."
-- Abraham Maslow
FP! (Score:-1)
At last!
Re: FP! (Score:2, Insightful)
Whoever chose struts 2 back then probably deserve it
Re: FP! (Score:4, Insightful)
Whoever chose struts 2 back then probably deserve it
Maybe not for the 6 months in which it was relevant, but for the 13[1] years where all java sweatshops kept on using that piece of shit yes, they deserve it.
[1]not a precise number
Re: FP! (Score:2)
I looked at struts2 back in my enterprise java days. There was way too much automagic driven by rails envy where it was doing very dynamic things magically based on the request. Lots of stuff where the request would become a very complex java object that would interact with automagic libraries to do dangerous things and you just had to trust their weren't any exploits. I decided to use json servlets and single page web app frameworks instead.
Re: (Score:2)
As long as it is clearly documented what it will do, and you know what precisely what it will having it automatically do things isnt necessarily bad, can save time, as long as finer grain control is allowed. If it is poorly documented and does unexpected things, this is pretty bad. Allowing a system command to be run is a pretty nasty undocumented automatic behaviour.
perspective (Score:2)
Whoever chose struts 2 back then probably deserve it
Maybe not for the 6 months in which it was relevant, but for the 13[1] years where all java sweatshops kept on using that piece of shit yes, they deserve it.
[1]not a precise number
Struts 2 is fine. It works fine. It with JSP/JSTL is all you ever need in the general case. Everything else is sugar (except few problem domains where you truly need something new.) I like Vaadim and Stripes, but I've seen enough sites VERY WELL built with plain old Struts and JPS/JSTL to know it is the wielder, not the tool.)
If you have a decently built system that runs well on Struts, why change it? Just to try something new? That's not engineering, that's playing on someone else's dime.
Every damned s
Re: perspective (Score:0)
dude.... you are confusing Struts and Struts 2. They have nothing in common but the name.
Re: perspective (Score:0)
Struts was the only thing available for a long time back in the dark ages of J2EE. So a lot of smart people were drawn into doing stupid things because that was the only thing available.
By the time Struts 2 came about it was about the time most smart people realised how stupid the whole J2EE thing was and abandoned it and starting trying out better things. Most stupid people went on to Struts 2.
Re: (Score:2)
Struts was the only thing available for a long time back in the dark ages of J2EE. So a lot of smart people were drawn into doing stupid things because that was the only thing available.
By the time Struts 2 came about it was about the time most smart people realised how stupid the whole J2EE thing was and abandoned it and starting trying out better things. Most stupid people went on to Struts 2.
That's an axiomatic, self-fulfilling statement. Congratulations.
Re: (Score:2)
dude.... you are confusing Struts and Struts 2. They have nothing in common but the name.
No, I just never cared to call them Struts and Struts 2. Both are fine, having worked on them both. I can see why why my lazy wording would confuse people, though.
Re: perspective (Score:0)
I think you just admitted you fall under the "you deserve it" and "stupid people" categories as pointed out by the various posters above.
Re: (Score:2)
I think you just admitted you fall under the "you deserve it" and "stupid people" categories as pointed out by the various posters above.
I'll say yes to that if it makes you feel... I dunno, accomplished? Sure, go for it, you win.
Re: perspective (Score:0)
Woohoo!
Re: (Score:2)
What would you recommend instead?
Re: (Score:2)
I acknowledge that it's not for everyone, but I'm really enjoying Vaadin [vaadin.com] right now.
Re: FP! (Score:0)
Vaadin came out much later than struts 2 so you can't say they deserve it for not choosing Vaadin.
Re: (Score:2)
Re: FP! (Score:0)
Vaadin wasn't known as Vaadin back then and really was not that popular until post 2009 or even later.
And no Millstone and IT Mills toolkit (Vaadin's old name) are not serious contenders when Struts 2 came out.
Considering Struts 2 came out with lots of hype and went out of favour very very quickly, I would say the peak of Struts 2 hype did not overlap with when Vaadin started getting popular.
Ok... unless you are talking about really really really stupid people who still chose Struts 2 after 2010. I think it
Re: (Score:0)
You precisely said "came out". You are just changing words to make it sounds like you were correct all along when you were not. Typical selfish moron
Re: FP! (Score:0)
Back then Spring MVC was already available. It survived much better because they kept things simple.
Re: FP! (Score:0)
Back then even staying on struts 1 was smarter than going with struts 2 which is a completely different framework and not a version upgrade.
People blindly jumped on Struts 2 because there was a time where everyone used Struts 1. Because.... hey who would want to have an iPhone 6 when an iPhone 7 is already out? It's so passe!