3 ms·
> build: ant, then maven and just when maven started getting massive traction, gradle I'm not sure that I would call 3 big build systems over the course of 20
by gred 12y ago
> build: ant, then maven and just when maven started getting massive traction, gradle
I'm not sure that I would call 3 big build systems over the course of 20 years "churn" :-)
> web frameworks: JSP, JSF, Spring MVC, Wicket, Tapestry, GWT, struts, dropwizard (and compiled java - Grails, Play etc...)
The height of the churn corresponded to people trying to handle MVC on the server side, and seems to have subsided somewhat as people have simplified the server side (RESTful APIs) and moved the MVC to the client side.
I wonder if this churn is somehow intrinsic to the type of problem being solved (user interaction), rather than to the technology / language / community.
- Illniyar 12y agoin regards to build, I was talking more about when these systems became popular/hyped/adopted rather then when they were released. Maven didn't became really adopted until 2.0 came out, and, to me at least, Gradle gained traction extremely fast after Maven was adopted (along with sbt for scala and others). I think Maven laid out the foundation for the adoption of gradle. But yes, it's a lot farther apart then Grunt vs Gulp. I was more trying to show that build systems change even for very stable languages/ecoSystems (relatively speaking). In regards to problem solved - it's an interesting thought, I haven't done a lot of ui outside of web, I wonder if other people can shed some light on churn regarding ui frameworks on desktop (or even flash/silverlight/unity etc...)
- empthought 12y agoThere is some churn in layout recommendation and widget availability, but the fundamental application construction model in iOS 8 is the same as it was for OpenStep 20 years ago.
- gred 12y agoOpen source; MVC; API stability -- choose two?