5 ms·
Our web product went from AngularJS to React to Angular to Angular + Spring. The addition of Spring helped us introduce a useful constraint: if you can build it
by zkirill 4y ago
Our web product went from AngularJS to React to Angular to Angular + Spring. The addition of Spring helped us introduce a useful constraint: if you can build it as an old-school page with Spring, don't put it into the SPA. Angular is reserved for deep core business logic and UI which would be impractical to build anywhere else. One of the biggest benefits is reducing our Angular project complexity, making it easier to keep current with Angular updates. I am happy to hear that SPAs are no longer sexy because this sounds like the landscape has matured. For example, Angular started doing LTS releases.
- dimgl 4y agoThis sounds needlessly complicated.
- zkirill 4y agoMaybe, shoot me an email if you want to chat about it kirill at getfillet.com
- arcturus17 4y agoNow your design system is probably all over the place and you have to know two ways to build a view, and have to decide every time which one to use.
- zkirill 4y agoYou invented a problem. SPA team and Spring team have separate responsibilities. Our customers don’t care how it looks beyond ergonomics and functionality. It took us a long time to shift away from “SPA all the things” mentality.