Introducing ASP.NET vNext

Re:Introducing ASP.NET vNext by edwinnathaniel on Monday May 12, 2014 @12:43PM (#7733810)

I'd say from capability perspective it's huge.

But capability is half of the story. Tooling/ecosystems is the other half (re: MonoDevelop is still not up to the snuff).

[ Parent | on HN ]

Re:Introducing ASP.NET vNext by malaporte on Monday May 12, 2014 @12:53PM (#7733878)

Yes. If only JetBrains could release an IntelliJ-based IDE for C#, that'd be nice.

[ Parent | on HN ]

Re:Introducing ASP.NET vNext by pionar on Monday May 12, 2014 @02:51PM (#7734652)

It really wouldn't be that hard, Roslyn's out there for compilation, and doing things like Intellisense.

[ Parent | on HN ]

Re:Introducing ASP.NET vNext by edwinnathaniel on Tuesday May 13, 2014 @02:35AM (#7736775)

IDE probably one big important piece, but I love to have Maven + its ecosystem for .NET (NuGet is not there, far from it).

[ Parent | on HN ]

Re:Introducing ASP.NET vNext by ragesh on Monday May 12, 2014 @12:52PM (#7733863)

That's a fair point, but now you can develop in VS on Windows and target pretty much every platform out there. They've also announced official support for Cordova, and they have the whole Xamarin thing going on. VS already has Python support, and Node.js tools are also being added.

This is starting to look like a pretty decent environment to work in.

[ Parent | on HN ]

Re:Introducing ASP.NET vNext by edwinnathaniel on Tuesday May 13, 2014 @02:37AM (#7736777)

I stopped using Windows for development platform for a while already.

While Windows ecosystems are gaining momentum, it's just not there yet.

Like you said it's just "decent environment", not better than what I use today.

[ Parent | on HN ]