3 ms·
> For example, I love angular, but migrating away from angular after using it for one year would doubtless be a very painful process. I wish AngularJS’s depend
by goblin89 12y ago
> For example, I love angular, but migrating away from angular after using it for one year would doubtless be a very painful process.
I wish AngularJS’s dependency injection/forced modularity and HTML augmentation/templating were somehow independent and not requiring each other.
> if I outgrew this, how difficult would it be to migrate away from it?
I'm becoming successful at fighting my urge to migrate my projects away from things I outgrow. I reason that changed preferences alone should not constitute a reason to rewrite an existing and working solution. And in case costs of adapting existing solution are higher than costs of rewriting it from scratch, then this is probably due to some unfortunate design decisions or obscure libraries/frameworks used, so these are the things to avoid.
- pluma 12y ago> I wish AngularJS’s dependency injection/forced modularity and HTML augmentation/templating were somehow independent and not requiring each other. That was why I eventually switched to React after trying to find ways to have Angular-like components/bindings without the DI/IoC parts of Angular (even going as far as reimplementing parts of Angular). If you only want the bindings, maybe rivets or knockout is an alternative?