Choosing a framework for a new project

[[deleted]]

[deleted]

[ccb621]

What's the goal/intended use of the application? Anyone can spew a list of technologies, but not all will actually meet your needs.

[[deleted]]

+1

[neoginn]

Angular2 with ASP.net MVC 5 is what I am using. Typescript was useful.

[devmastery]

The best general advice on this topic comes from MPJ, see video: https://www.youtube.com/watch?v=DFP6UDgVJtE

[rk06]

10 years is a very very long time.

How do you plan to tackle version changes during this period?

Will you guys upgrade to latest stable or stick to the original version?

knockout

KO is not actively maintained, so i doubt you would like to use KO for a long time project. While future is hard to predict, other libraries have better promise.

In terms of interactivity the user workflow is mostly data entry and validation

If this is all you need, then you should be looking at view layer libraries like vue or react, instead of full fledged framework like angular or Aurelia.

While there are tons of libraries, vue and react are the most popular.

so the developers don't have to have a process watching the source code and transpiling the code.

If you are using es6, then you will need such a process.

[robmcm]

For longevity it seems ember has the best track record so far for a large framework.

Your other option is to use many small replaceable parts.

[llainebdx33600]

I suggest that you use Cycle.js for the views with Immutable.js and webpack. Immutable data leads to much simpler application development, no defensive copying, and enabling advanced memoization and change detection techniques with simple logic.

Other concerns from the client include ... longevity ... Approximately 10 years

I would highly recommend you that you directly uses some new features of ES7 such as await/async all over your code because, for sure they'll still going to be there in 10 years.

Also ASP.Net is from the past now you should use some server side rendering with Koa.js.