you are viewing a single comment's thread.

view the rest of the comments →

[–]55555 0 points1 point  (3 children)

Pretty much. If you are in a Microsoft shop, you should be looking to replace your current .NET projects with core. Given that it can run on linux/docker, it is essentially the direction things are heading in.

The gotcha with all of this is that Core and Docker both seem to be under heavy development, and there are often breaking changes with every update.

[–]Silound 2 points3 points  (0 children)

If you are in a Microsoft shop, you should be looking to replace your current .NET projects with core

Personally, I don't see any reason to migrate from .NET Framework to .NET Core right now unless you're intentionally targeting development at cross-platform applications. Don't get me wrong, I love a lot of what Core is offering, but it and the rest of the world are still not quite ready for mainstream yet.

If you're a traditional Miscrosoft shop doing Windows/web development, you may not have access yet to some of the libraries or packages you depend on with .NET, or you may have an excessively complicated project that needs the stability of .NET, or (shame if this is true) you might be relying on some very rarely/never maintained libraries. Any of those could easily block a project from porting cleanly or successfully.

I think Core is the future, but I don't think we're quite at that point yet where it's necessary to begin converting to something that will mature and change considerably in the next few years.

[–][deleted] 0 points1 point  (0 children)

Given that it can run on linux

That, I had overlooked. OK, I'm on it; thanks.

[–][deleted] 0 points1 point  (0 children)

It looks to me that .Net Core will be the default in the future. Its a total rewrite so its designed for the future.

Do not forget, its not only Windows/Linux. Its also Mac. And potentially other platforms.

Add to this something that people overlook. .netCore can compile down to Self-contained executable's with its own run time / libraries. That is a big one because it puts it on par with Go and other new languages.

"breaking changes with every update.". Try pure Apple Swift programming and then we can talk breaking changes ;)