Comment by aerophilic | Hacker News Reader

Comment by aerophilic | Hacker News Reader

Parent Full thread

I agree, they can do a better job articulating what is “awesome”.

For me personally, there are 3 main reasons that I have been super excited about .Net core:

1. It is C#, in my opinion the best statically typed language. The easiest way I have described it to other folks is it is Java++. Combine it with really good intelligence, and it is like the code “flows out of you”. Part of the reason for that is the effort put into the language itself (getters/setters, lambda functions, etc), but equally and possibly more important is the support of Microsoft, so this is a language/toolset that is being used daily to make itself better. (In my opinion this is why Jetbrains is so good, the developers use their own tools constantly).

2. It is cross platform from the ground up. I can’t understate how great it is to have an alternative to java

3. Rosleyn: being able to compile and potentially be as fast as C++

Just my 2 cents

> 3. Rosleyn: being able to compile and potentially be as fast as C++

Roslyn is the C#/VB compiler and analysis tool. Yes, that allows you to compile C#. No, it doesn't have anything to do with performance. That's where other things come in, like RyuJIT, or .NET Native.

For someone who is not well versed in MS world, what is the C# equivalent of the Java Streams API?

LINQ, the IEnumerable extension methods, and IQueryable extension methods.

I'd like to point out that the extension method feature of C# is one big reason why I like this whole story much better than the Streams API in Java. There are often methods I wish were part of the IEnumerable interface, and with extension methods, I can add them myself! (if they are not already provided in, say, MoreLinq [1]). Very convenient, and a big boost in productivity.

https://github.com/morelinq/MoreLINQ

having a look at it, it seems like LINQ?

I had no idea what Java Streams was (a long time since I wrote much Java) and it appears to be the Java version of LINQ:

https://www.foreach.be/blog/java-and-net-comparing-streams-l...

I would say IEnumerable<T> interface.

linq, kind of, but it has more run time overhead and is more flexible.

Java streams is the awful copy of LINQ, written something like 7 years later.

Reply on news.ycombinator.com