5 ms·

.Net core seems really cool, but I don't see it getting anywhere for a while. Most of the enterprise is still using .Net standard. It is near to impossible for

.Net core seems really cool, but I don't see it getting anywhere for a while. Most of the enterprise is still using .Net standard. It is near to impossible for me to get a job working on an ASP.Net Core codebase right now, because everyone seems to still be using .Net standard.

nerdywordy 10y ago
Fair point. For enterprise the transition will likely take 3-5 years minimum before Dot Net Core really catches hold. But for startups or faster moving enterprise shops, Dot Net Core does present a more exciting (and flexible) ecosystem.
tboyd47 10y ago
Interesting. What is preventing them from upgrading? I ask because I was thinking of picking up .NET Core as a stepping stone to one day transitioning to a Microsoft-based skillset (I'm a Ruby dev). If it's proving to be unpopular within the .NET community then I may reconsider.
- artimaeis 10y ago
  Enterprises generally don't upgrade anything unless someone convinces them it's necessary. They don't want to follow the bleeding edge of tech, they want to follow the most stable/secure tech with the largest pools of talented workers. Hence the popularity of Java and .NET at the enterprise level. Picking up .NET core would make a great start to transitioning to a Microsoft-based skill set. That's generally the way those skills are gained - by starting with the latest available to the platform and working backwards as necessary. I started down the path with .NET 4.5 and don't think I've had but a small handful of opportunities to utilize the features in it because most of the servers I work with have .NET 4 as the latest version.
- Slump 10y ago
  Most enterprise's on .NET are windows shops. There is very little incentive in my opinion to run .NET core when you're a windows shop as it doesn't provide any real-world benefits/features yet that are beyond what you get from the full .NET framework. .NET Core's story as it stands is making .NET properly cross-platform. If you don't need cross-platform at the moment you don't net .NET core in my opinion.
- tonyedgecombe 10y ago
  I wouldn't say it's unpopular, just not ready yet. Most .Net development is for corporations and they tend to be conservative about new technologies.
- dmarlow 10y ago
  I think the reason that migration isn't happening faster is because of the dependencies a project may have that don't yet support .net core. That one PDF or SAML library that's on full .net only prevents the move.
nlawalker 10y ago
Assuming that by ".Net standard" you mean the traditional .NET Framework, the irony in this comment is awesome. .NET Standard is the newest of the new. https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introduci... The terminology is getting hard to follow :)
- jamesmp98 10y ago
  Whoops! Yeah, all this is sorta making me put off getting into the Microsoft Stack.

nerdywordy 10y ago

Fair point. For enterprise the transition will likely take 3-5 years minimum before Dot Net Core really catches hold. But for startups or faster moving enterprise shops, Dot Net Core does present a more exciting (and flexible) ecosystem.

tboyd47 10y ago

Interesting. What is preventing them from upgrading? I ask because I was thinking of picking up .NET Core as a stepping stone to one day transitioning to a Microsoft-based skillset (I'm a Ruby dev). If it's proving to be unpopular within the .NET community then I may reconsider.

artimaeis 10y ago
Enterprises generally don't upgrade anything unless someone convinces them it's necessary. They don't want to follow the bleeding edge of tech, they want to follow the most stable/secure tech with the largest pools of talented workers. Hence the popularity of Java and .NET at the enterprise level. Picking up .NET core would make a great start to transitioning to a Microsoft-based skill set. That's generally the way those skills are gained - by starting with the latest available to the platform and working backwards as necessary. I started down the path with .NET 4.5 and don't think I've had but a small handful of opportunities to utilize the features in it because most of the servers I work with have .NET 4 as the latest version.
Slump 10y ago
Most enterprise's on .NET are windows shops. There is very little incentive in my opinion to run .NET core when you're a windows shop as it doesn't provide any real-world benefits/features yet that are beyond what you get from the full .NET framework. .NET Core's story as it stands is making .NET properly cross-platform. If you don't need cross-platform at the moment you don't net .NET core in my opinion.
tonyedgecombe 10y ago
I wouldn't say it's unpopular, just not ready yet. Most .Net development is for corporations and they tend to be conservative about new technologies.
dmarlow 10y ago
I think the reason that migration isn't happening faster is because of the dependencies a project may have that don't yet support .net core. That one PDF or SAML library that's on full .net only prevents the move.

nlawalker 10y ago

Assuming that by ".Net standard" you mean the traditional .NET Framework, the irony in this comment is awesome. .NET Standard is the newest of the new. https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introduci... The terminology is getting hard to follow :)

jamesmp98 10y ago
Whoops! Yeah, all this is sorta making me put off getting into the Microsoft Stack.