Is that really such a bad thing? Are we not dependant on getting new projects? Isn't there value in the progress that is made in js and similar fast moving technologies?
I agree that the pace of js and web is a little over the top and most applications would probably work just as well with the technologies from 10 years ago, but having an envirement that is moving forward has it's good sites for sure :D
#ActuallyAutistic web dev. Does front of the front-end. Loves perf and minimalism. Prefers HTML, CSS, Web Standards over JS, UX over DX. Hates div disease.
If you're working on projects that don't need further development then those are irrelevant to the point. In that kind of setting you use whatever you want to get it done fast, and to meet whatever the requirements. And I guess when working on continuous stream of projects you do want things to change constantly to spice it up.
Working on long term projects that continue as long as you can imagine are a bit different story. One of the issues with front end code is that you really want there to be as little of it as possible, and writing it from a JS-centric perspective results to a lot of code that shouldn't be in the front end. This code has maintenance and performance worries and when development continues for multiple years it really starts to hurt. It would be much better to not create the problem in the first place by greatly diminishing use of JS on the browser side.
Is that really such a bad thing? Are we not dependant on getting new projects? Isn't there value in the progress that is made in js and similar fast moving technologies?
I agree that the pace of js and web is a little over the top and most applications would probably work just as well with the technologies from 10 years ago, but having an envirement that is moving forward has it's good sites for sure :D
If you're working on projects that don't need further development then those are irrelevant to the point. In that kind of setting you use whatever you want to get it done fast, and to meet whatever the requirements. And I guess when working on continuous stream of projects you do want things to change constantly to spice it up.
Working on long term projects that continue as long as you can imagine are a bit different story. One of the issues with front end code is that you really want there to be as little of it as possible, and writing it from a JS-centric perspective results to a lot of code that shouldn't be in the front end. This code has maintenance and performance worries and when development continues for multiple years it really starts to hurt. It would be much better to not create the problem in the first place by greatly diminishing use of JS on the browser side.
When you say it like that, I can see the problem/frustration more clearly :D