|
|
|
|
|
|
by EdwardDiego
1595 days ago
|
|
|
I think it really depends on your framework. Good ones have upgrade paths that work. "Move fast and break things" frameworks are not good ones. My first job, I was working on a Tapestry 5 web-app. Very nice framework, very opinionated though. And the creator, Howard L Ship, was very opinionated about breaking things. So we could never upgrade past 5.x (where I think x was 4 or 6), because it just broke everything for us, and we put weeks of dev time into trying to overcome that. In the end, we just ported the app to Wicket, it was faster to do so. |
|
|