Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Understanding .NET 2015

blogs.msdn.com

Post reply on HN
Print view View original

11–20 of 107 posts

Re: Understanding .NET 2015

#11

Post by rjbwork »

untog wrote: post #3
rdtsc wrote: post #2

Recently I got to use some C# on Linux (with Mono framework), and I gotta say it wasn't bad. I didn't do anything with GUI elements, was all back-end server code. C# wouldn't be my top "go to" language, but I would put it above Java. I liked some of the generics handling better, it can be less verbose it seems. Monodevelop is not on par with Visual Studio, but it is solid and worked well for me. I usually don't like…

I used to work in C# (now mostly live in JavaScript land) and I miss things like LINQ a lot. So here's hoping we see wider adoption of C# in the future.

I'm primarily a C# guy, but whenever I touch JS, i find Underscore indispensable.

Re: Understanding .NET 2015

#12

Post by cpayne »

Eyas wrote: post #8

What I still don't understand in this picture is the what does the future look like in terms of the .NET framework . .NET Core sounds great, and its great that they are unifying the implementation, not just the API, for many of the "app models". But, its unclear to me if there's the intention for .NET Core to fully succeed .NET Framework at some point in the future. Or, rather, will some of the app models we see on t…

I think the reason why the future isn't spelt out is because they don't know (or haven't decided). The last 12 months have been massive steps for Microsoft (open source, multi platform). I would expect they would wait and see how their customers & community react.

Also Azure is a massive component to all of this (they make money of Azure, they don't make a massive amount of cash from someone using .Net).

Microsoft have a long history of keeping old versions alive (unlike say Apple). Eg Internet Explorer, Windows XP, Office, Win Forms vs MVC

I'm sure .Net core will take over one day. In the same way .Net 4.5 overtook .Net 2 / 1.1 etc.

Re: Understanding .NET 2015

#13

Post by untog »

emodendroket wrote: post #9
untog wrote: post #3

Earlier quoted context omitted.

I used to work in C# (now mostly live in JavaScript land) and I miss things like LINQ a lot. So here's hoping we see wider adoption of C# in the future.

It's pretty trivial to implement Linq-like functions in JavaScript, or, I think stuff like undersocre has them.

It is and it isn't. LINQ is actually incredibly smart under the hood, so if I ran:

    myList.Where(x => x.name = 'Person');
          .Where(x => x.age > 18);
          .ToList();
it wouldn't actually run two different array filters - it would combine them. You can imagine the performance gains to be had there.

Re: Understanding .NET 2015

#14

Post by bad_user »

edgyswingset wrote: post #5
rdtsc wrote: post #2

Recently I got to use some C# on Linux (with Mono framework), and I gotta say it wasn't bad. I didn't do anything with GUI elements, was all back-end server code. C# wouldn't be my top "go to" language, but I would put it above Java. I liked some of the generics handling better, it can be less verbose it seems. Monodevelop is not on par with Visual Studio, but it is solid and worked well for me. I usually don't like…

> I liked some of the generics handling better, it can be less verbose it seems. It pays off in spades in a lot of situations, but the biggest I've noticed is Android development. Hitting a network from a button press in Xamarin is as simple as: button.OnClick += async { var data = HitTheNetworkForSomeData(); // Note that since this is still async, // you may want to set a global or have a // different approach to ha…

You don't need to use Java for Android or for the JVM, you can just use Scala. See Scaloid [1] for setting up Scala for Android and Scala Async [2] to get that nice "async" syntax you've mentioned.

[1] https://github.com/pocorall/scaloid

[2] https://github.com/scala/async

Re: Understanding .NET 2015

#15

Post by avens19 »

edgyswingset wrote: post #5
rdtsc wrote: post #2

Recently I got to use some C# on Linux (with Mono framework), and I gotta say it wasn't bad. I didn't do anything with GUI elements, was all back-end server code. C# wouldn't be my top "go to" language, but I would put it above Java. I liked some of the generics handling better, it can be less verbose it seems. Monodevelop is not on par with Visual Studio, but it is solid and worked well for me. I usually don't like…

> I liked some of the generics handling better, it can be less verbose it seems. It pays off in spades in a lot of situations, but the biggest I've noticed is Android development. Hitting a network from a button press in Xamarin is as simple as: button.OnClick += async { var data = HitTheNetworkForSomeData(); // Note that since this is still async, // you may want to set a global or have a // different approach to ha…

This. The amount of new Thread(new Runnable(){...}).start() I have in my Android code is awful. And then inside the Thread you have to use runOnUiThread() to change UI stuff. Given how common it is for an app to hit the network, this should be much much easier. Looking at your example it might be slightly easier but it also isn't inlineable. C# solves both of these problems

Re: Understanding .NET 2015

#16

Post by 0x0 »

It looks like the open source cross-platform version of .NET, v5 ("core"?), is something that was written completely from scratch?

Why wouldn't they open source the v4.x version? And why is WPF, Windows Forms, and ASP.NET placed above the .NET 4.x block in the diagram?

Is .NET v5 Core a from-scratch lightweight reimplementation that can't run the full stack? If not, why the huge separation?

Re: Understanding .NET 2015

#17

Post by frou_dh »

troycarlson wrote: post #7
untog wrote: post #3

Earlier quoted context omitted.

I used to work in C# (now mostly live in JavaScript land) and I miss things like LINQ a lot. So here's hoping we see wider adoption of C# in the future.

I spend most of my time in C# and it's always a sad moment when I start typing .Where(x => ...) in another language and realize it doesn't exist.

It's spelled filter

http://en.wikipedia.org/wiki/Filter_%28higher-order_function...

Re: Understanding .NET 2015

#18

Post by stinos »

There are spelling squiggles in the article's first image :]

http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-bl...

Apart from that: I'm really curious and sort of excited to see what the next years will bring in terms of development using .Net in general and C#/F# specifically, on multiple platforms.

Re: Understanding .NET 2015

#20

Post by untog »

frou_dh wrote: post #17
troycarlson wrote: post #7

Earlier quoted context omitted.

I spend most of my time in C# and it's always a sad moment when I start typing .Where(x => ...) in another language and realize it doesn't exist.

It's spelled filter http://en.wikipedia.org/wiki/Filter_%28higher-order_function...

I don't mind C# not using that name because .Where doesn't actually filter the object, it returns an IQueryable, which you can chain further statements onto, then filter.
Post reply on HN