News for hackers. Stuff that matters.
Re:Introducing ASP.NET vNext by ragesh on Monday May 12, 2014 @12:40PM (#7733785)
As someone who recently moved from C# to working with Node, Angular and Python full time, the recent announcements definitely make me want to go back to using .Net again. I love where all of the new stuff is headed.
Re:Introducing ASP.NET vNext by UK-AL on Monday May 12, 2014 @12:50PM (#7733850)
I've worked with various languages C#, Python, Ruby, Objective-C(I was an iOS developer) but I prefer strongly typed languages for larger projects, and the refactoring tools that it allows for.

Eventually I would like a completely statically typed inferred language, go mainstream(Aka Demand for it)

C# is my best option atm.

Re:Introducing ASP.NET vNext by ragesh on Monday May 12, 2014 @12:54PM (#7733882)
I agree. My recent forays in to javascript have left me wanting to rewrite big chunks of my new app in TypeScript instead. :)
Re:Introducing ASP.NET vNext by olmo on Monday May 12, 2014 @01:28PM (#7734101)
Fortunately rewrite in typescript is mainly rename the files, simplify class declarations and add some type annotations as you go
Re:Introducing ASP.NET vNext by path411 on Monday May 12, 2014 @01:42PM (#7734208)
Make the jump to TypeScript, you will be glad you did.
Re:Introducing ASP.NET vNext by badman_ting on Monday May 12, 2014 @12:59PM (#7733925)
I moved away from C# and .NET about 4 years ago, and use all those things too. The recent developments are great, but I view them more as a cool glass of water for people in a hot place (not hell, far from it).

I don't like how .NET as a platform/ecosystem/community lags on certain things that are almost taken for granted in other areas, like deployment tools and package managers. Then again, when I worked with .NET those things were my responsibility so I guess their lack affected me more than many .NET devs.

Re:Introducing ASP.NET vNext by UK-AL on Monday May 12, 2014 @01:05PM (#7733966)
Well the good news is that those things are standard now.
Re:Introducing ASP.NET vNext by troygoode on Monday May 12, 2014 @01:25PM (#7734083)
Yes, those are standard now because they're "old" in the rest of the industry. It remains to be seen if newer tech that is starting to become standard outside of the Microsoft ecosystem today (containers, for example) will be integrated fast enough to matter.
Re:Introducing ASP.NET vNext by troygoode on Monday May 12, 2014 @01:33PM (#7734144)
I mean containers like docker. https://www.docker.io/
Re:Introducing ASP.NET vNext by PallarelCoedr on Monday May 12, 2014 @03:47PM (#7735008)
It's 'Drawbridge'[0,1] in the windows world and it is on it's way apparently.

You can run mono in linux containers which means you can run this stuff too.

[0] http://www.zdnet.com/microsoft-to-offer-its-drawbridge-virtu... [1] https://research.microsoft.com/en-us/projects/drawbridge/

Re:Introducing ASP.NET vNext by UK-AL on Monday May 12, 2014 @01:28PM (#7734103)
Containers? You mean like MEF(Included in .net framework) or Unity?

.Net has always had containers like that.

Re:Introducing ASP.NET vNext by Guillaume86 on Monday May 12, 2014 @01:56PM (#7734307)
No he mean ressources isolation containers (tiny VMs)
Re:Introducing ASP.NET vNext by UK-AL on Monday May 12, 2014 @02:21PM (#7734485)
I don't know how they would do that with windows, since it requires features in the linux kernel.
Re:Introducing ASP.NET vNext by Aaronontheweb on Monday May 12, 2014 @03:33PM (#7734924)
Starting with Windows 8, Hyper-V (Microsoft's virtualization platform) is built into the OS - and one of the goals with it was to be able to virtualize different environments invisibly to the end-user.

The Hyper-V team have also been actively committing to the Linux kernel for many years now, and I'm happily running a 6-node Cassandra cluster on my Windows 8 dev machine right now using Hyper-V :)

So it's not there yet, but ground has been broken.