5 ms·
Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.
by tracker1 9y ago
Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.
- kirse 9y agorenewed interest Maybe in the Hacker News bubble. Outside of that, things have been cruising along quite nicely for at least a decade.
- tracker1 9y agoI've worked with .Net devs for most of the past 17-18 years... I've done my fair share of C# development beyond that. And I've seen a lot of shops move away from .Net. Several to Node.js, others to Java or Ruby. It's not just a Hacker News bubble. I'm working in a place now, where most new development is .Net core to be deployed in Linux. There are also a few node projects, and go is also approved for new projects. Being able to target and deploy cross platform is huge.
- wutwutwutwut 9y agoThats an odd way to phrase it considering v1 was released 15 years ago. Like saying I've spent almost half of the last 10 years with my 4 years old son.
- c0nfused 9y agoIt always seems odd to me that people are excited about .net coming to Linux or osx. Mono has been around for so long I can't remember when it showed up, 2001? As far as I know mono's been feature complete for a decade or more. .net core is neat, but for me it's a tooling thing and not a "we can write .net of Linux" thing
- littlecranky67 9y agoWell, before .net core, Mono never had support for the most important frameworks that were commonly used in .NET world. Namely no support for WPF, EntityFramework, WebAPI, WCF (partial support came later on). This was a dealbreaker for most windows devs. If you accepted this and went for open source alternatives and/or mono's own frameworks (NHibernate, Gtk#, ServiceStack etc.), mono was pretty solid.
- westcoastdev 9y agomono has been around but was very buggy outside of Xamarin based apps. .net core is a first class .net implementation using lots of the same code code from .net framework and works much better in high stress server workloads.
- ComputerGuru 9y agoMono has never put a focus on reliability or production-ready code. It's been awesome for desktop software and client applications, but we actually deployed ASP.NET on Mono to unify our deployment environment across our web infrastructure and ran into random bugs and show stoppers on a daily basis. And I'm not just talking about the horrible process of getting Visual Studio projects to deploy to a Mono server, the unavailability of certain APIs, functions that don't quite work the same way, or issues with the Mono frontend server, but also runtime infrastructure issues, random crashes, and more that made it a horrible nightmare worth maintaining two different operating systems for (our reliance on PHP for WordPress and vBulletin (back then, now XenForo instead of vB) meant we faced basically the same .NET-on-Linux issues with PHP-on-Windows, prevented us from going all-Windows at the time). .NET Core is actually cross-platform from the ground up and the .NET Core team considers it blocking issue and won't release if the codebase doesn't run properly and identically on all supported platforms. It's a night-and-day difference.
- martinald 9y agoI agree, I've been using mono in semi-production for the best part of a decade for ASP.NET and it's been a complete nightmare every time. It's also a shame that VS for Mac is so half baked for web projects despite MSFTs backing. This issue I have been search for an answer for a while is so obvious I don't understand how they didn't catch it: https://stackoverflow.com/questions/43967326/visual-studio-mac-cant-run-asp-net-core-project https://stackoverflow.com/questions/43967326/visual-studio-m...
- scarface74 9y agoLuckily there is a better alternative.... https://www.jetbrains.com/rider/ https://www.jetbrains.com/rider/
- dewiz 9y agoI love Rider but since they went GA it's super expensive. VS for Mac beta channel is decent, then there's VSCode which is free
- alkonaut 9y agoI got excited about running mono about 5 minutes every year for the last decade. Each time the enthusiasm came to a complete halt when I actually tried it. Core is in a much better position in terms of completeness, reliability, user friendlyness and not least usage. You always felt like you were the only person trying C# on Linux years ago. Not so now.
- maxxxxx 9y agoMy company uses .NET mainly so it's nice to see these libraries. But from recent experience with several of them I am starting to be a little wary of .NET SDKs. It seems most .NET SDKs are either buggy, incomplete or have some other issues. It feels like you are a second class citizen with .NET. I would prefer if I could call Java SDKs from .NET. These SDKs seem to be higher quality than most .NET SDKs. C# is a great language and .NET is good but for the availability of 3rd party libraries I would probably go the Java route if I had to start from scratch.
- mattchamb 9y agonot sure i would go this route, but you can actually call java libraries from .net using a project called IKVM. I used it for a toy project and it seemed to work
- Kipters 9y agoIKVM development has been halted: http://weblog.ikvm.net/ http://weblog.ikvm.net/
- jackfoxy 9y agoDevelopment halted, yes, but AFAIK rock solid up to current Java release.
- gwenzek 9y agoSo sad to learn about that. Ikvm was so great! It was really granting you access to all the Java world in .Net I hope it will find a new developer. Microsoft should pay someone to do it IMHO
- maxxxxx 9y agoI don't understand why MS hasn't been supporting IKVM already. It makes .NET a much more viable option for many projects. There are a lot of Java libraries out there for which .NET has no equivalent or only low quality ports.