4 ms·
Personally I had much more problems with mono 1 year ago then .NET core today. Also, I run multiple website with databases, gb of record processing in queues e
by romanovcode 9y ago
Personally I had much more problems with mono 1 year ago then .NET core today.
Also, I run multiple website with databases, gb of record processing in queues etc. Also I'm building CI runner on .NET core and so far I've got 0 problems. so I would not call it "hello world".
I have 99 problems but .NET Core ain't one.
- shadowmint 9y agorubbish. I don't believe it. If you haven't had problems with .NET Core, you haven't used it in a serious capacity. I'm not even going to bother to go into the details; anyone is free to look up the issue list and the endless stream of issues, its all on github. The versioning, the nuget support, the package.json stuff, the huge fuss over targeting netcoreapp for the 2.0 preview... .NET Core is the future, but its not here yet. Its the closest its ever been with the new preview release, but honestly, I'm deeply sympathetic to other early adopters. Migrating to .net standard 2 will be painful. Anyone thinking of using core right now: dont. Wait at least for the 2.0 release version to roll out, or you're building on quicksand.
- devwastaken 9y agoWhat are you writing? .NET Core doesn't even impliment many things that Mono and .net framework do yet.