4 ms·
> Pick a library, stick with it, stop jumping to the next framework and the churn stops. I wish it were that easy. At work, we've picked angular 1, and now the
by perlgeek 8y ago
> Pick a library, stick with it, stop jumping to the next framework and the churn stops.
I wish it were that easy. At work, we've picked angular 1, and now there's angular 5, which is a totally different framework (and the migration path only works well if you did everything juuuust right), and no clear policy on how long angular 1 will be maintained.
So either we churn, or we have no idea how long there will be any support.
- underwater 8y agoThis is the risk in the authors advice to just pick a monolithic framework. We’ve been building a React framework. We’ve been careful about how we choose components to use, so there has been very little churn. And because we control the implementation we’ve been able to build things we could never have done with a library like Angular.
- hvs 8y agoThey made a fair number of mistakes with Angular.js (1), so the rewrite was a sensible, if painful change for early adopters. Since version 2, the model has remained relatively stable with changes being improvements rather than completely breaking.