3 ms·
I don't think you'll find anyone who thinks it's hard to build 1 SPA without a framework. The thing is that if you build 2, 3, 100, you'll find yourself doing
by nicc 9y ago
I don't think you'll find anyone who thinks it's hard to build 1 SPA without a framework.
The thing is that if you build 2, 3, 100, you'll find yourself doing the same stuff over and over again (and always better than the previous time, so that you'll want to replace all your old code, which is now obsolete), and that's when frameworks are useful.
- mLuby 9y agoand when you hire and work with others, it's better if they already know and agree with how to do things rather than having to learn your custom SPA.
- nkkollaw 9y agoYup. Well said, that's definitely another good reason to use a framework.
- ourmandave 9y agoso that you'll want to replace all your old code, which is now obsolete), and that's when frameworks are useful. You know, like Angular 1.
- jchw 9y agoIt ain't an easy transition, but transitioning from Angular 1.x to Angular 2.x can be done. A path forward was forged in 1.x updates that let you incrementally make your code more Angular 2-y. Also, there doesn't seem to be a huge breaking change in the foreseeable future either. That being said, React seems far less likely to pose this threat, with the caveat that you do have smaller pieces you may have to rewrite as the ecosystem evolves. That being said, in a few years of using React, the only things that have hugely changed are: 1. React Router 2. Use of ES6 classes 3. Better compilers/tools ...That's it. And the latter 2 don't really mean you need to rewrite code, although often you can to take advantage of new stuff. All in all, not at all a raw deal. You get a lot from the work.
- rehemiau 9y agoSee, you don't always need a SPA, you know.