3 ms·
This stability does mean that old React (or Knockout, or whatever) applications will still work just fine for the end users, likewise without a single line chan
by lelandfe 2y ago
This stability does mean that old React (or Knockout, or whatever) applications will still work just fine for the end users, likewise without a single line changed.
The instability is on the tooling side (and peer deps). Getting back into a project that uses Broccoli and Bower is a nightmare. And that was just a handful of years ago. You have to become a detective, finding what combination of package versions and Homebrew dependencies were expected on the last git commit date.
- 0x000xca0xfe 2y agoI know, I've had to revive and make small changes to an old Angular project myself. Which is my point. If the underlying technology hasn't really changed, why constantly break the tooling and compatibility in general? This collective lack of discipline is exactly why I don't work in FE. It's just tiresome for no actual reason.
- coffeebeqn 2y agoI also haven’t seen it in any other place. Game dev and backend which I’ve worked in uses the same technologies for decades. It’s like someone trying to write a book but instead of writing a new chapter each month they mess about with their ink choice and their font choice and their paper roughness and get very little actual progress
- hyldmo 2y agoI will note that Bower’s last non-hotfix release was 8 years ago :)
- lelandfe 2y agoI’ve got big hands!
- cube00 2y ago> This stability does mean that old React (or Knockout, or whatever) applications will still work just fine for the end users, likewise without a single line changed. Not in the current enterprise cyberops environment of needing to pass dependency security scans at all times.
- lolinder 2y agoIt still works fine for end users, just not for the compliance department.
- deleted 2y ago[deleted]