|
|
|
|
|
by softwaredoug
1702 days ago
|
|
Im curious what you anticipate the longevity of your app to be? Lots of things are possible. My last company has a fairly critical Angular 1 app from early 2010s. Guess what, it works! It’s ~9 years later and going strong. It has a big enough team to keep the lights on, and only now is it probably reaching a serious inflection point. But IMO if I had to do it again and cared about longevity I’d avoid a framework. I would probably also avoid JavaScript, and maybe even putting much complexity in the web tier. Instead I’d probably find a way to get my business logic in a CLI and make any clients fairly disposable. |
|
It might as well happen with Blazor, if it's kept further maintained as a part of .NET normal release cycles for years to come, and won't be stripped out in some next major release.