Across the world, .NET teams starting new projects are sitting in a precarious position and asking themselves the same question:
Should I Use ASP.NET 5 (right now)?
If you believe the ASP.NET team's roadmap, ASP.NET 5 is right around the corner, March 31st being the official end of Q1. That is a hard 77 days.
I've been speaking with team members, and I will list some of the positive comments and concerns echoed by many of them:
- "If we don't go with ASP.NET 5, we are building our future on expiring tech (.NET 4.6)."
- "The new ASP.NET 5 model is designed to work better for web development."
- "A nicer workflow for devs and designers."
- "It's still C#! While the infrastructure may be new, it is still familiar."
- "Gulp makes build tasks fun."
- "Cross-platform is awesome."
- "I'd rather not defer the pain of upgrading, let's take that on now."
- "It's not cool for team members who are new to .NET to have them learn two paradigms within a 6-month span."
- "Are we just chasing the 'new and shiny`?"
- "Tools and libraries we've become familiar with may not be available. The current Nuget ecosystem is broad."
- "We may be betting the business on 'untested' and 'unstable' technology."
- "The learning curve could take us longer to deliver value to the business."
- "We are more likely to make mistakes because so much is unknown."
- "What bugs are waiting for us? Are there showstoppers?
For a team starting a new project, ASP.NET 5 might not feel like the obvious choice right now. This statement may come off as obvious, but you can't build software without a technology stack. Picking the right one for your team and stakeholders is a tough decision. Many facets should be considered that extend beyond the "cool" factor. Personally, building on ASP.NET 5 is slightly a better choice than writing a system on .NET 4.6. I'm more afraid of getting stuck in past, than running face first into the future with a chance of nosebleeds.