[manscrober]

>Worse still all of those libraries are deprecated now, so if I want to do it again, I'll need to start again from scratch and select a new animation library.

This is why I stopped being interested in modern web anymore. Everything is deprecated at unbelievable pace, you can't keep track of it unless you work full time in the field. If it was all for great efficiency and performance, I'd get it, but it seems to just follow the newest fad every 2 years. Maybe with wasm that could change, but I'll believe it when I see it.

[capableweb]

> Everything is deprecated at unbelievable pace, you can't keep track of it unless you work full time in the field.

Is this really true? The same JavaScript I wrote 3 years ago still work, for multiple different applications. It's really uncommon that browsers break "user-space" JavaScript, I can't even remember the last heavily dependent API that got removed and cause havoc.

What does change very often is the latest trends/fads in JavaScript frameworks/UI libraries, but if you pick one and stick with it, it won't magically break because JavaScript changed. I think what's causing your problem is here is the want/need to stick with the latest flavor of frameworks/libraries instead of becoming deeply familiar with one and sticking with it.

[noduerme]

3 years is no time. I have userland code that still works 15 years on. The problem is only if I want to change from jQuery 1.x or some ancient CSS library... it would break completely. I can live with that. What I can't really live with is the 500,000 loc I wrote in Actionscript 3 being permanent unusable and unable to run anywhere, ever again. That kind of thing makes you never want to work on another project.