Struts 1.3 的替代品有哪些
我的产品目前使用 Struts 1.3 进行 Web GUI 开发。这或多或少是作为一项组织指令强加给我们的。最近，我们遇到了问题。主要的一点是其陡峭的学习曲线 - 最近加入团队的新 Web 开发人员已经习惯了 Spring MVC，需要几周的时间才能使用它来提高工作效率。
我们已经就是否应该寻找 Struts 1.3 的替代品进行了一些讨论。我们的 Web GUI 很快就会有很多新功能，我不确定是否值得从头开始使用新的 Web 框架。根据我通过与一些经验丰富的 Web 开发人员（在我当前的组织之外）交谈以及我自己在网络上的研究得出的信息，Struts 1.3 是一个稳定、成熟且相当流行的框架（Apache Struts 页面声称它是 最流行的 Web 框架，但我对此持怀疑态度）。
你有什么意见？
My product presently uses Struts 1.3 for web GUI development. This was more or less thrust upon us as an organizational directive. Of late, we are having problems with it. The main main point is its steep learning curve - the new web developers who came into the team recently are used to Spring MVC and require several weeks before getting productive with it.
We've had a few discussions on whether we should look for alternatives to Struts 1.3. Our web GUI will soon have a lot of new features going into it and I'm not sure whether it is worth the effort to start from scratch with a new web framework. From what I have gathered by talking to a few experienced web developers (outside my current organization) and from my own research on the Net, Struts 1.3 is a stable, mature and fairly popular (the Apache Struts page claims that it is the most popular web framework, but I take it with a pinch of salt).
What are your opinions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们的意见无关紧要。当您在 SO 上提出这样的问题时，没有提供有关您的情况、您遇到的问题类型（除了新人不知道之外）、您未来的需求是什么、您正在考虑替代方案等详细信息，那么人们倾向于使用他们最喜欢的框架来响应，无论是 Spring、Wicket、JSF、Stripes、GWT 等，此时这些框架都与你无关。
您的需求是什么？ Struts 是否满足这些要求？
如果 Struts 有效并且您有丰富的使用经验，那么为什么要抛弃它并改用其他东西呢？因为新员工不知道，必须花几周时间学习？如果不投入一些时间，他们应该如何学习呢？通过渗透？如果您担心花费的时间，那么只雇用已经了解 Struts 的人，而不是在工作中培训他们。
如果您必须更改框架（因为您达到了其限制），那么您已经对 Spring MVC 有了一些专业知识，因为新开发人员知道这一点，所以 Spring 可能是一个不错的选择。
或者您可以遵循迁移的逻辑路径（或者至少看起来合乎逻辑）并切换到 Struts 2。但Struts 1和2有很大不同，所以你仍然需要学习新的东西并投入时间，但至少有更多的资源比较 Struts 1 与 Struts 2，而不是 Struts 1 与 JSF。
好吧……废话已经够多了……我个人的意见是首选 Spring，然后是 Struts 2。我不能推荐其他的，因为我没有做过 JSF、Wicket 等。
所以基本上，它继续了解每个框架的功能并选择最适合您需求的。
Our opinions are irrelevant. When you ask a question like that on SO, without providing details about what your situation is, what kind of problems you are having (besides new people not knowing it), what your future needs are that you are considering alternatives to it etc, then people have a tendency to respond with their favorite framework, be it Spring, Wicket, JSF, Stripes, GWT etc which at this point becomes irrelevant to you.
What are your needs? Does Struts fulfill them or not?
If Struts works and you have a lot of experience with it, then why throw it away and change to something else? Because new hires don't know it and must spend a few weeks learning it? How are they supposed to learn it without investing some time? By osmosis? If you are worried about that time spend then only hire people who already know Struts instead of training them on the job.
If you have to change framework (because you reached its limit) then you already have some expertize with Spring MVC since the new developers know that, so Spring could be a good choice.
Or you could follow the logical path of migration (or at least it seems logical) and switch to Struts 2. But Struts 1 and 2 are very different, so you still need to learn something new and invest time in it, but at least there are a lot more resources comparing Struts 1 to Struts 2 than Struts 1 to JSF for example.
OK... enough rambling... my personal opinion would be to go for Spring as a fist choice then Struts 2. I can't recommend others since I didn't do JSF, Wicket etc.
So basically, it resumes in finding out what the features of each framework are and choose the best for you needs.