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…
Understanding .NET 2015
21–30 of 107 posts
Re: Understanding .NET 2015
#22It 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
#23Re: Understanding .NET 2015
#24Recently 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…
"we'll start seeing more back-end usage of .NET." Outside of startup world, it is already used everywhere.
Re: Understanding .NET 2015
#25Re: Understanding .NET 2015
#26Earlier quoted context omitted.
> 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
#27Recently 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…
Re: Understanding .NET 2015
#28It 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?
I don't think it's written from scratch. Why would it be? WPF and Windows Forms have some Windows specific stuff that would be irrelevant in a cross-platform version.
I remember looking at the corefx github project just after the announcement, and it was very sparse with just a few commits and classes; it looked a lot like a brand new project written from scratch.
This wording also makes it sound like ".net core" is a re-boot, scorched earth reimplementation which will take some time to reach the levels of the original .net:
>.NET Framework 4.6
>The .NET Framework is still the platform of choice for building rich desktop applications and .NET Core doesn’t change that.
>For Visual Studio 2015 our goal is to make sure that .NET Core is a pure subset of the .NET Framework. In other words, there wouldn’t be any feature gaps. After Visual Studio 2015 is released our expectation is that .NET Core will version faster than the .NET Framework. This means that there will be points in time where a feature will only be available on the .NET Core based platforms.
Re: Understanding .NET 2015
#29Earlier quoted context omitted.
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.
_.where(listOfPlays, {author: "Shakespeare", year: 1611});
Re: Understanding .NET 2015
#30Recently 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…
Just out of curiosity, what is your go-to language? C# is probably my favorite general purpose language so far, although I really prefer Golang's goroutines/channels over C#'s async model. Curious to hear other perspectives!