Skip to main content
deleted 53 characters in body
Source Link
LazyCoder
  • 617
  • 1
  • 4
  • 11

My team is about to build a new user interface. The team has skills in a range of client-side and server-side technologies. Half the team argue for ASP.NET MVC, and half the team argue for a JavaScript SPA. Either technologies works with our business requirements.

The main point of contention seems to be how to survive the SPA framework churn. E.g Everyone feels more certain Microsoft will be around supporting ASP.NET in 10 years, but we don't feel as certain about a framework like React.

People seem to have addressed this problem with server-side components through the use of industry standards, interfaces and dependency injection.. but there doesn't seem to be the equivalent options for frontend frameworks.

How can we elevate fears of framework lock-in?

Dependency injection, reliying on standrds

My team is about to build a new user interface. The team has skills in a range of client-side and server-side technologies. Half the team argue for ASP.NET MVC, and half the team argue for a JavaScript SPA. Either technologies works with our business requirements.

The main point of contention seems to be how to survive the SPA framework churn. E.g Everyone feels more certain Microsoft will be around supporting ASP.NET in 10 years, but we don't feel as certain about a framework like React.

People seem to have addressed this problem with server-side components through the use of industry standards, interfaces and dependency injection.. but there doesn't seem to be the equivalent options for frontend frameworks.

How can we elevate fears of framework lock-in?

Dependency injection, reliying on standrds

My team is about to build a new user interface. The team has skills in a range of client-side and server-side technologies. Half the team argue for ASP.NET MVC, and half the team argue for a JavaScript SPA. Either technologies works with our business requirements.

The main point of contention seems to be how to survive the SPA framework churn. E.g Everyone feels more certain Microsoft will be around supporting ASP.NET in 10 years, but we don't feel as certain about a framework like React.

People seem to have addressed this problem with server-side components through the use of industry standards, interfaces and dependency injection.. but there doesn't seem to be the equivalent options for frontend frameworks.

How can we elevate fears of framework lock-in?

Source Link
LazyCoder
  • 617
  • 1
  • 4
  • 11

Mitigating frontend framework lock-in fears

My team is about to build a new user interface. The team has skills in a range of client-side and server-side technologies. Half the team argue for ASP.NET MVC, and half the team argue for a JavaScript SPA. Either technologies works with our business requirements.

The main point of contention seems to be how to survive the SPA framework churn. E.g Everyone feels more certain Microsoft will be around supporting ASP.NET in 10 years, but we don't feel as certain about a framework like React.

People seem to have addressed this problem with server-side components through the use of industry standards, interfaces and dependency injection.. but there doesn't seem to be the equivalent options for frontend frameworks.

How can we elevate fears of framework lock-in?

Dependency injection, reliying on standrds