News for hackers. Stuff that matters.
Re:The End of IKVM.NET by slg on Saturday April 22, 2017 @06:26PM (#14175191)
>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?

Re:The End of IKVM.NET by devwastaken on Sunday April 23, 2017 @12:31AM (#14176510)
Just 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.

Re:The End of IKVM.NET by shouldbworking on Sunday April 23, 2017 @12:51AM (#14176571)
I'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...

Re:The End of IKVM.NET by GordonS on Sunday April 23, 2017 @06:43AM (#14177562)
I seem to be in the minority here in being largely happy with the .NET OSS ecosystem. Look at github or nuget - it's rare I can't find a library to fulfil my needs.

The only issue I really do have is down to fragmentation - library authors have too many targets to supports support. Libraries may support .NET Standard, but not the .NET framework before 4.6, for example.

Re:The End of IKVM.NET by shouldbworking on Sunday April 23, 2017 @07:21AM (#14177678)
You are definitely in the majority among .NET engineers. Like everything it seems like people get pigeonholed into certain families of tech after being in the field for a while. Microsoft is one of those families, and so is Java.

.NET community ain't terrible, but it's nothing compared to Python and Java. I have tried to convince my co-workers of this fruitlessly over the years but basically all of them are .NET for life. There's no point in arguing that another product is better if the person you're arguing with has never seen it.

I used to share the same opinion as you until a few years ago when I got bored of making the same old .NET CRUD "line of business" apps at work. I decided to do some cool open source stuff that I always enjoyed reading about.

At first I wanted to use .NET but I quickly abandoned it after playing with Linux on AWS and learning about Cassandra, React, rabbitmq, elastic search, and Postgres. I had never even touched all of these great things. At an MS shop it's "SQL Server, SQL Server, SQL Server" for anything with even the slightest resemblance to data storage. Web development is "Angular" or "MVC" with little variation.

I started writing some cool open source stuff and realized I would be alienating myself from most of my users if I made it in C#. So, I picked up Java and never went back, at least at home.

I'm the only developer at our company out of ~35 that prefers Java over C# and the only one that contributes to free software. I don't think that correlation is a coincidence.

Re:The End of IKVM.NET by GordonS on Sunday April 23, 2017 @03:14PM (#14179864)
It's true that I don't use Python or Java (although I have used it in the past - wasn't a big fan, and now C# seems so mch more powerful) and do use Typescript and (unfortunately!) Javascript. Python is something I do want to get into though, just to find out for myself.

There are some great .NET libraries for working with RabbitMQ, such as EasyNetQ, Chinchilla and more recently I'm loving RawRabbit. There are also good libraries for working with ElasticSearch, and I use Marten a lot for using Postgres as a document store (great library).

The place I work is indeed an MS shop, but we're all open minded and use other stuff occasionally at work, and quite often outside of work. Maybe we're in the minority there too though; I know plenty .NET devs who do have tunnel vision, but I suppose you get that across al languages.

Re:The End of IKVM.NET by polskibus on Sunday April 23, 2017 @05:09AM (#14177276)
I'm curious, in what areas is Java 100x faster than C#?
Re:The End of IKVM.NET by _pmf_ on Sunday April 23, 2017 @05:55AM (#14177407)
Aggressive inlining and devirtualization is one thing. Escape analysis that allows objects that one would expect by all rational and technological reason to be required to be allocated on the heap being allowed to be allocated on the stack.
Re:The End of IKVM.NET by zigzigzag on Sunday April 23, 2017 @08:23AM (#14177885)
It's not just a handful of optimisations. The entire JVM is performance focused in a way the CLR just isn't. Microsoft historically put their resources into the C# language and the IDE. Sun/Oracle put their efforts into the runtime.

For instance, the CLR doesn't do any profile guided or speculative optimisations at all. That's a 20% win for most Java apps and even more still for languages with higher levels of abstraction like Scala. So right there from the start .NET is 20% behind. The CLR doesn't have an interpreter, so, it spends a lot of time JIT compiling code that isn't particularly important. That takes CPU time away from your app, not sure how much of an effect that is but I can imagine it's at least another 10% down. C# asks devs to control de-virtualisation by hand to try and compensate, but the JVM can do a better job automatically. CLR is only now starting to look at tiered compilation and even then only a very basic form compared to Java which has had it since Java 8.

But not only is the base infrastructure and approach far more advanced, the JVM's JIT compilers are way ahead of even the new RyuJIT. Not just fancy optimisations like devirt and escape analysis/scalar replacement, but even basic things like profile-guided basic block ordering. JVM can do auto-vectorisation of loops, lock optimisations, it can even replace speculatively profile and replace synchronised blocks with hardware (TSX) transactional memory. The CLR is multiple generations behind where HotSpot is. And the JVM team is extending its lead even further with projects like Graal.

Re:The End of IKVM.NET by shouldbworking on Sunday April 23, 2017 @06:03AM (#14177432)
Not a ton of places, but in my case forwarding HTTP requests. Netty is close to 100x faster than regular .NET. Another example is JSON serialization. Jackson/GSON are maybe 30x faster than the built-in JSON handling in C#. Everyone smart uses Newtonsoft now, but it was a huge bottleneck until a few years ago.

.NET seems to have a lot of rough edges where MS said "fuck it, nobody will complain if this is slow". If you happen to use one of those features that didn't get enough love you get burned. Java is generally polished throughout, most likely due to the sheer volume of software written for the JVM

Re:The End of IKVM.NET by venture_lol on Sunday April 23, 2017 @02:23PM (#14179528)
It is faster practically everywhere from 2x and on...
Re:The End of IKVM.NET by snuxoll on Saturday April 22, 2017 @11:54PM (#14176382)
As 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.

Re:The End of IKVM.NET by djhworld on Sunday April 23, 2017 @04:08AM (#14177101)
> 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?

Re:The End of IKVM.NET by zigzigzag on Sunday April 23, 2017 @07:42AM (#14177747)
.NET is primarily used by two cultures that don't place a big emphasis on open source development: Windows and giant in-house enterprise IT projects, often at banks. Banks have historically struggled with open source: it took a long time for them to start using it, and much longer still to start contributing.

Java's focus on cross-platform support from the start probably seemed like a waste of resources back in the 1990s when Windows was so dominant, but it had the advantage of making it more popular amongst UNIX users and the existing open source culture. Java going open source long before .NET also contributed to this. The end result is that you get organisations like Red Hat, Apache, IBM that create vast quantities of high quality open source Java code, and a culture that is steeped in open source development. Whereas in .NET it's rare to use components not built by Microsoft and when they do exist they are typically proprietary, same as in the 1990s.

Re:The End of IKVM.NET by rsynnott on Sunday April 23, 2017 @07:13AM (#14177653)
Until very recently, .NET has only really been usable on Windows. Nobody uses Windows for 'web scale' (ugh) stuff; it's expensive and historically was difficult to automate. So there's less incentive to make really high quality libraries for it; Guava would never happen, say, because companies like Google don't use Windows.
Re:The End of IKVM.NET by nl on Sunday April 23, 2017 @05:19AM (#14177311)
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.

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

Re:The End of IKVM.NET by voltagex_ on Sunday April 23, 2017 @04:32AM (#14177166)
Could it just be time? Since VS Community was released, there's no huge blocker for someone to develop for .NET (other than Windows itself).
Re:The End of IKVM.NET by _pmf_ on Sunday April 23, 2017 @06:25AM (#14177513)
95% of companies cannot use VS Community Edition because their revenue is too high.
Re:The End of IKVM.NET by shouldbworking on Sunday April 23, 2017 @12:51AM (#14176572)
Oh my God I feel exactly the same. At home I don't touch C# if I can avoid it
Re:The End of IKVM.NET by pdwetz on Saturday April 22, 2017 @06:35PM (#14175245)
They 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).
Re:The End of IKVM.NET by johncolanduoni on Saturday April 22, 2017 @07:56PM (#14175600)
Something 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.
Re:The End of IKVM.NET by cm2187 on Sunday April 23, 2017 @01:30AM (#14176693)
My 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).

Re:The End of IKVM.NET by adw on Sunday April 23, 2017 @02:24AM (#14176846)
Python is popular in science because

a) it had f2py at a really important (early) point

b) matlab is insanely expensive.

Re:The End of IKVM.NET by j_s on Saturday April 22, 2017 @10:56PM (#14176204)
The 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.

Re:The End of IKVM.NET by taspeotis on Saturday April 22, 2017 @06:39PM (#14175256)
The author's twitter sheds some insight (scroll down a bit): https://mobile.twitter.com/JeroenFrijters
Re:The End of IKVM.NET by Operyl on Saturday April 22, 2017 @06:43PM (#14175274)
At 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.
Re:The End of IKVM.NET by taspeotis on Saturday April 22, 2017 @06:58PM (#14175344)
Yes 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?"