2 ms·
The problem with using a framework is that the upgrade tax is steep. Every major version change is basically an Armageddon. This is one reason why micro servi
by didip 4y ago
The problem with using a framework is that the upgrade tax is steep.
Every major version change is basically an Armageddon.
This is one reason why micro service design is popular, you can throw away everything later.
- 42e6e8c8-f7b8-4 4y agoI think that says more about the maintainers than libraries vs framework. Some maintainers value backwards compatibility and some don't. Some value the time of their users more than the purity of their platform/framework. React as a framework seems to value it's users -- upgrading isn't that hard. Angular 1 to 2 didn't. Microsoft and x86 worship backward compatibility -- 30 year old programs frequently run without a hitch on the PC platform, thus showing that they value backward compatibility. Anything written against a Google sdk or api or platform will need to be reworked every 2-3 years or the app will break.