7 ms·
>I’ve slowly been losing faith in .NET. That piece is interesting. I don't know many .NET developers that aren't excited with what Microsoft has been doing wi
by slg 10y ago
>I’ve slowly been losing faith in .NET.
That piece is interesting. I don't know many .NET developers that aren't excited with what Microsoft has been doing with .NET over the last couple years. Can anyone shed light on why someone would be losing faith in it?
- j_s 10y agoThe best analogy I can think of is that .NET has gone chasing after the Node.js development experience. (And, much more speculatively: has at least the potential to keep a lot of the worst from both what it was and what it is trying to become.) In any case, the current transition has pros and cons, and even these are categorized differently by each dev. In addition, there are new alternatives that could cater to a particular dev's exact style.
- pdwetz 10y agoThey mentioned .Net 3.5, which is ancient by modern programming standards; if I had to guess, the general direction towards generics, dynamic, and functional support? But take that with a huge grain of salt. This post is from a library author, so their opinion is probably going to vary a lot with application developers (especially those of us who never did much with Mono, but are utilizing Core already in production with Linux).
- taspeotis 10y agoThe author's twitter sheds some insight (scroll down a bit): https://mobile.twitter.com/JeroenFrijters https://mobile.twitter.com/JeroenFrijters
- Operyl 10y agoAt the same time his blog post states that his recent twitter doings aren't completely the true cause here. Makes you wonder what else happened.
- taspeotis 10y agoYes I read the blog. My comment is an attempt to help answer the GP's question ("Can anyone shed light on why someone would be losing faith in it?") not "why did IKVM end?"
- johncolanduoni 10y agoSomething I know has been a big roadblock for IKVM is the fragmentation of .NET with all the different profiles. The main branch of IKVM only works with the full .NET framework versions, not WinRT/Silverlight/Xamarin etc. There was a fork that supported Xamarin iOS but it was very rough and there hasn't been much interest in it since RoboVM and Multi-OS Engine came onto the scene.
- snuxoll 10y agoAs someone who is paid to do .Net development, I'm continually disappointed by the .Net ecosystem. .Net core SHOULD be awesome, but I'm not seeing much movement in it the areas I particularly care about (like the SDK for our ECM, database drivers for the IBM i) as well as the larger open source ecosystem. Honestly, I'm much happier writing stuff in Java or Python than I am .Net - both have substantially healthier ecosystems and I feel like I'm getting work done BECAUSE of my tools rather than in spite of them. I have to suck it up at work most of the time because we are a ".Net shop", but any personal projects I work on will likely never be done in C# unless it's a Windows desktop app.
- shouldbworking 10y agoOh my God I feel exactly the same. At home I don't touch C# if I can avoid it
- djhworld 10y ago> as well as the larger open source ecosystem. There must be a reason for this though, one of the reasons why Java has a good ecosystem is because it's had a huge head start in terms of time and mindshare. At the same time though, what's stopping people from making the open source ecosystem in .NET really good? There must be a reason, is it cultural?
- voltagex_ 10y agoCould it just be time? Since VS Community was released, there's no huge blocker for someone to develop for .NET (other than Windows itself).
- _pmf_ 10y ago95% of companies cannot use VS Community Edition because their revenue is too high.
- nl 10y agoThere must be a reason for this though, one of the reasons why Java has a good ecosystem is because it's had a huge head start in terms of time and mindshare. This doesn't seem to be a complete explanation. I was doing Java heavily in the early 2000s, and open source Java was pretty new still. Apache Struts[1] was possibly the first big OS Java project, and it was only released in 2000. The first version of .NET was released in 2002, and something like Rails was only released in 2004. "Head start" doesn't seem to explain this. [1] https://en.wikipedia.org/wiki/Apache_Struts_1 https://en.wikipedia.org/wiki/Apache_Struts_1
- devwastaken 10y agoJust look at VS 2017. A rushed IDE that has all sorts of weird quirks and bugs, non-backwards compatible with VS15 extensions, and now you have to actually create a MS 'insider' account and go through some broken web pages to get the VS15 download. Microsoft is abandoning their software just as fast as JS does now. For something that is built for actual desktops and servers that will run for years and most likely does not have a maintenance team, I think thats dangerous. Now we take in .net core, which has changing standards and incompatible build files between various versions it has released. To even get .net core V2 you've gotta go to their github releases and grab a beta build. By having VS15 and VS17 with .netcore 2, my toolchain broke and couldn't even compile any modern .net core projects, requiring full wipe of VS. Combine that with working on projects that could be written for .net framework, .net standard, or mono, and you've got one big ball of mud that nobody wants to touch. Maybe in 5 years if things standardize and multi-platformability becomes a real goal of MS, but right now, its easier and more stable to make multi-platform applications with electron than C#. Or just C++ and QT, or really any other language that doesn't have 4 different runtime versions.
- shouldbworking 10y agoI've been a .NET developer for years but I've also been a big Java guy. The lack of an OSS ecosystem in .NET is a huge glaring problem. This is compounded by the echo chamber that is the MS developer world. There have been multiple projects where lack of a library or database driver have resulted in hacks or passing something to a little Java app and back because it's unrealistic to do the work in C#. Like I said, the MS world seems to be an echo chamber and the vast majority of C# devs shun any solution outside official MS channels. Why do they do this? Because open source devs generally still dislike MS and until .NET core (which is not ready for prime time) using C# saddled you to Visual Studio, Windows, SQL Server, and IIS. Because of this, the open source community on other languages like Python or Java is maybe 20x bigger. The other reason open source avoids the MS platform is because they like to take your stuff and replace it with the "MS official" version. Entity framework was originally a poor emulation of NHibernate. WebApi a copy of Spring Boot. Instead of helping your project, or making it official like Java tends to do, MS likes to replace your OSS with something proprietary. The other big .NET problem is speed. I like C# syntax better, but when I wanna get something done on my own I reach for Java first. It's faster and more flexible. In some areas the execution speed difference is 100x. The CLR might be quick but MS never considered performance a priority until .NET core, because before core they were only competing with themselves. The echo chamberyness is leaving the MS stack in the dust. Everyone else runs on Linux now. Everyone else is using containers and SPA frameworks and Postgres. In the MS world, the unofficial rule is that if it's not a visual studio project template don't use it. It encourages reaching out of the Microsoft ecosystem as little as possible. Big sites like stackoverflow that have chosen to go with C# have blogged about their adventures. Most of these adventures involve building things that are already available from the community in most languages. Core may save .NET but it might be too little too late. Windows has already lost the war for server operating system and that leaves little reason to use C# over the primary competitors Java and Go. Both of those have ecosystems far larger and far better support for things like databases, mapreduce, Linux, containers, etc...
- polskibus 10y agoI'm curious, in what areas is Java 100x faster than C#?
- cm2187 10y agoMy main grief again .net now is rather that it has lost its simplicity. There are multiple frameworks to do the same things. For desktop you have winform, wpf, windows 8 apps, universal windows apps, xamarin, etc. For interoperability you have pcl, .net core, .net standard, mono/xamarin, etc. For web development you have webforms, mvc, mvc core. When they introduce a new language feature like tuples, you need to load some external libraries to be able to use it, it doesn't work straight out of the box. And I fear that as they will try to integrate all of this while keeping backward compatibility it will create yet even more fragmentation. Simplicity is I think why python is so popular and why it is even used in all sort of odd places (like doing computationally intensive maths).
- adw 10y agoPython is popular in science because a) it had f2py at a really important (early) point b) matlab is insanely expensive.