Re:The Frontend Treadmill
by 0x000xca0xfe on Thursday March 20, 2025 @12:14PM
(#43425192)
I 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.
Re:The Frontend Treadmill
by coffeebeqn on Thursday March 20, 2025 @12:57PM
(#43425722)
I 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
I will note that Bower’s last non-hotfix release was 8 years ago :)
I’ve got big hands!
> 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.
It still works fine for end users, just not for the compliance department.
Depends on your SecOps. Ours shuts down apps with critical vulnerabilities if they're not patched within 48 hours.
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.