Re:JavaScript-heavy approaches are not compatible with long-...
by paulryanrogers on Monday February 16, 2026 @07:55PM
(#47042349)
React--for all its warts--hasn't had a major backward compatibility break. Microsoft Windows selling point for a long time was backward compatibility.
Re:JavaScript-heavy approaches are not compatible with long-...
by jamesfinlayson on Tuesday February 17, 2026 @01:34AM
(#47044366)
> If in 2010 I'd know that the damn thing would die in 2021
Was it obvious back then? I had to work on an AngularJS site for a while and it was the most confusing thing ever. Having come from React I couldn't understand the complexity but maybe it was still better than callback hell in jQuery?
Re:JavaScript-heavy approaches are not compatible with long-...
by mikrotikker on Tuesday February 17, 2026 @10:22AM
(#47048457)
This is why I struggled and struggled to omit JS at all costs on a greenfield project - many apps from even 5 years ago by now fired teams fail to build with cryptic npm messages. And if you get past that you have to deal with webpack or some such junk. We settled with go fyne which compiles to wasm to handle both local and remotely accessible use cases. Trade off is not as much freedom and a fixed feature set but I know it's gonna work after 5 godamn years.
I also at some point inherited an app written in Vue 2. By the time I got it, Vue 3 was already out and a couple of years later, Vue 4, completely different to Vue 2, was out. Rewriting was not an option, so I had to create a docker image that can compile the damn thing offline, cause if some part of the supply chain breaks, well, that's it.
Ten or eleven years is not a super long time in enterprise software. Having to keep upgrading and changing libraries just cause the devs of the libraries get bored should not be a thing.