4 ms·
> You're telling me you updated YOUR code to work with the latest framework release? I work on frontend right now, but I've worked on backend earlier, as well
by golergka 2y ago
> You're telling me you updated YOUR code to work with the latest framework release?
I work on frontend right now, but I've worked on backend earlier, as well as gamedev and desktop applications. And it was always like that in every area: when your major dependency has a major version upgrade, you will have to spend effort on migrating your code to support it.
- bastardoperator 2y agoIt a software problem, not a frontend/backend problem. We've all been subjected this insanity in some way.
- int_19h 2y agoIts severity varies between ecosystems, though, and JavaScript is especially crazy in this regard. Frontend JS, doubly so.
- fiddlerwoaroof 2y agoThe issue I had when I still worked in the frontend world is the frequency of major version updates. If you used standard project bootstrapping tools in approximately 2017, you got a whole bunch of libraries and tools that would have significant breaking changes multiple times over the next three years or so (I know because I had to maintain them).
- 2mlWQbCK 2y agoThat seems to be a problem that is getting worse with time though, with increasingly frequent "major" releases and fewer that consider backwards compatibility much at all. Also it used to be much more common to have published specs and standards that you could code to for a good chance to not have to rewrite your code next month.
- leosarev 2y agoExcept usual time to upgrade to next version of .net is less than man day.