5 ms·
I just wish more company adopt .net instead of java, the new .net core thing is a game changer. C# is a good language, combined with the runtime that can run an
by robertwt7 5y ago
I just wish more company adopt .net instead of java, the new .net core thing is a game changer. C# is a good language, combined with the runtime that can run anywhere? it's even better. The thing is enterprise companies mostly went with the safe route which is java, or most that use .net are stuck in the old version.
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)
- bob1029 5y agoThe new .net has been amazing for us. Biggest QoL improvement would be the self contained deployments. We do B2B software, and being able to email a customer a zip that is guaranteed to work on any windows server without bullshit has been beyond incredible. Our customers love the experience too. We switched to SQLite for persistence, so there are literally zero prereqs to an install now.
- ed25519FUUU 5y agoOne of the reasons I love Go. Does the .zip file also contain the runtime? E.g., nothing is required to be installed on the remote system?
- codenesium 5y agoYes. .net now has self contained builds. The whole deploy can be a single executable with some caveats.
- VikingCoder 5y agoMy biggest hold-out for using C# at a medium-sized company would still be how awful Projects and Solutions are, when working with a big team. I'd have to develop my own tooling, first.
- DaiPlusPlus 5y agoI don't see how that could possibly be a problem. 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.
- VikingCoder 5y agoWell, that's good to hear. We had problems where you would add some dependencies, and I would add the same dependencies, but the GUIDs would be different, and then everything was impossible to merge. You're saying that's gotten better?
- hnrodey 5y agoSounds like you were doing something wrong to manage your solution files.
- hackerfromthefu 5y agoTo be fair every now and then the project files would get messed up by the tooling, and happened more often with nuget. It's still rare though and can be fixed by digging in to what's going on, or just recreating the projects and readding the source files.
- hnrodey 5y agoOur repo has nearly 15k .cs files across 700 .csproj files. If we can do this successfully, I think anyone can.
- codenesium 5y ago
- hulitu 5y ago> I just wish more company adopt .net instead of java, the new .net core thing is a game changer. C# is a good language, combined with the runtime that can run anywhere? it's even better. 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".
- kittiepryde 5y agoI'm curious about what is going on while .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?
- hackerfromthefu 5y agoIt's compiling interpreted code into machine code that's specific to the processor it's running on. Without this step it can still run but being interpreted it runs slower.
- pjmlp 5y agoWorking on a polyglot consulting company, one reason that doesn't happen is that .NET hasn't fully embraced cross platform like Java. 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.
- lloydatkinson 5y agoIs your knowledge out of date? .NET Core is no more, we're on .NET 6 now. 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.
- zsims 5y agoAll the Win32 component libraries, WPF, Entity Framework + extensions. There's oodles of these packages on nuget
- pjmlp 5y ago.NET 6 is .NET Core renamed. 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.