4 ms·
The problem with relying on these high-level frameworks, or heavy frameworks of any kind, is that one day they will change their entire approach to how things s
by renegade-otter 1y ago
The problem with relying on these high-level frameworks, or heavy frameworks of any kind, is that one day they will change their entire approach to how things should be implemented, and then you have a giant pile of legacy on your hands.
I learned that lesson the hard way with ExtJS 3 => 4, and now my wife claims I have commitment issues.
- tcoff91 1y agoThey are close to finally stabilizing the API (as much is possible given underlying platform stability). New Architecture has been in the works for 8 years. It’s such a massive upgrade over legacy architecture. Migrating our app to new architecture was not that hard tbh.
- chamomeal 1y agoReact-router has betrayed me so many times…
- aegypti 1y agoThat package’s churn single handledly changed my career path during the days of react 0.x away from FE. I think it was on v2 or v3? I still feel anger hearing its name the better part of a decade later.
- sokol-alxs 1y ago"high-level frameworks" no different to native OS APIs. Apple/Google is constantly releasing new APIs, changing old one, deprecating, etc. The difference is only in the velocity of changes/updates.
- bokchoi 1y agoOoh, I felt this one. I went through porting a webdav browser widget from ExtJS 2.1 -> 3 and then 3 -> 4. It was a nightmare. Does ExtJS still not html encode replacement values in it's templates by default?
- mardifoufs 1y agoSo, just like regular android development? But at least with some multiplatform support? Sign me up!