Hopefully it will change for c#, MS needs something for startups / enterprise / new dev to excite them to choose .net core! (despite all the bad things in the past)
Hopefully it will change for c#, MS needs something for startups / enterprise / new dev to excite them to choose .net core! (despite all the bad things in the past)
Our customers love the experience too. We switched to SQLite for persistence, so there are literally zero prereqs to an install now.
Outside Windows you only get a subset of the ecosystem, so you always have to watch out for libraries that have been written or ported to .NET Core explicitly, as a large majority of them might work on .NET Core on Windows, but fail everywhere else due to what they are using from Windows/COM.
Additionally there are 15 years of .NET Framework ecosystem that can't be easily migrated to .NET Core due to breaking changes.
Java doesn't suffer from this problem.
What libraries are you referring to, because outside of niche things like WCF there's very little left that doesn't run on every OS .NET 6 runs on now. Of course COM won't run on Linux.
Niche stuff like enterprise in-house build built 2002 and 2015 when Windows was the only game in town (mono wasn't really taken seriously), enterprise CMS like Sitecore and SharePoint, GUI frameworks (component libraries from DevExpress, ComponentOne, Telerik among others).
And all the stuff Visual Studio Professional/Ultimate have on the box and Rider will never support, nor VSMac/VSCode.
I'd have to develop my own tooling, first.
Yes, the old (pre-.NET Core), .csproj files were a mess, but the post-2017 .csproj/.props/.targets files are a pleasure to work with.
Yeah. Much better. Until you try to run it from a network share. Or your quad core laptop "Intel inside " goes in thermal throttling because .NET is "optimizing".
I haven't seen something like that, my laptop is AMD though? (I write .net code) Unsure how much of a difference that makes.
I like .Net, it's not without it's issues, I think the same is true with Java, having been the administrator for some Java servers in the past, I've seen plenty of Java issues that seemed crazy ~ but I think we're talking about how great things are now, maybe, while saying it doesn't matter because how bad the legacy tech is?
Without this step it can still run but being interpreted it runs slower.