4 ms·
Is the argument here that there are too many JS frameworks, or that the complexity of the frameworks themselves tends to grow over time? If the former, totally
by kelnos 4y ago
Is the argument here that there are too many JS frameworks, or that the complexity of the frameworks themselves tends to grow over time?
If the former, totally agree. If the latter, Java frameworks are plenty complicated.
Also not sure how you've missed a lot of other frameworks; Spring and J2EE are certainly not the only ones that have been around for 10+ years. Dropwizard, Vert.x, akka-http, GWT, Play... just to name a few.
- kkapelon 4y agoThe argument is that I could learn Spring in 2002, find a Job then I could learn Spring in 2008 and find a job and then I could learn Spring in 2013 and find a job and then learn Spring in 2018 and find a job and then learn Spring in 2023 and find a job. Spring IS complex, but you learn it once and you are done with it.
- intrasight 4y agoOr learn Cobol in 1965, find a job. Learn Cobol in 2022, find a job. Or Fortran - which I started using in 1983. Or C# (2000 for me) I think the key distinction is that these languages and libraries evolve over time.
- agos 4y agothis is really useful if you know in advance which framework is going to stay around twenty years. If you invested in GWT...