News for hackers. Stuff that matters.
Re:ASP.NET Core – 2300% More Requests Served per Second by snuxoll on Thursday February 18, 2016 @06:15PM (#11130156)
Unless you want to use F#, then it's an awful time because it still doesn't support .Net Core :(
Re:ASP.NET Core – 2300% More Requests Served per Second by abrodersen on Thursday February 18, 2016 @06:51PM (#11130396)
I was able to get my F# code to compile using .NET Core yesterday! It's difficult to find the correct project.json parameters and you have to build the latest CLI yourself, but it works.
Re:ASP.NET Core – 2300% More Requests Served per Second by louthy on Thursday February 18, 2016 @07:36PM (#11130606)
I used fsharp-dnx. The problem was it then doesn't support non .NET core targets. So for library development it's a real pain in the arse when you want to build multiple .NET targets (net45,net46,dnx...) with the same project.json.

The whole thing is a total mess at the moment, so I'm personally going to stay away from dnx until MS produce something that's close to their old RTM quality releases. It seems there's even a rival system with the dotnet CLI.

So I disagree strongly with the OP, it's not a great time to be a .NET developer. The improvements to C# and F#, yes, fantastic. But the ecosystem around it is so brittle at the moment; which is something that we never had to deal with in the past, and was one of the big selling points of the MS ecosystem.

Re:ASP.NET Core – 2300% More Requests Served per Second by pbz on Thursday February 18, 2016 @08:37PM (#11130914)
It's still in development. In the past you weren't even able to glance inside the sausage factory. If you want something solid then wait until 1.0 is out, preferably 2.0.
Re:ASP.NET Core – 2300% More Requests Served per Second by louthy on Thursday February 18, 2016 @09:14PM (#11131057)
Thanks for the history lesson. I am fully aware of what stage it's at. I am commenting on the solution and what appears to be a meandering target, with huge holes. It's currently at RC but no support for F#, no support for SignalR, VS2015 tooling is comically bad, cripplingly slow build times, and now a totally new toolchain (dotnet-CLI) that doesn't support the same dependency system that dnx supports.

That doesn't sound like a RC to me. I have a general feeling that the RTM standards are slipping massively at MS. Windows 10 was a dog when I tried it - and obviously not finished, VS2015 is very unstable, then the issues above... It feels like stuff is being pushed out the door much earlier than it previously would have been.

I do appreciate the direction they're taking, it just feels rudderless atm.

Re:ASP.NET Core – 2300% More Requests Served per Second by pbz on Thursday February 18, 2016 @10:43PM (#11131385)
They may call it RC, but it's barely beta. Recently they said they'd take their time to get it right - less conference driven development. This is a new start, SignalR will come after RTM, so lots of things won't be there. Think of it as version 1 rather than 5. There's currently no VB support either, so F# may take a bit.
Re:ASP.NET Core – 2300% More Requests Served per Second by snuxoll on Thursday February 18, 2016 @07:41PM (#11130630)
dotnet-cli is supposed to be a replacement for DNX. Personally, I'm trying to push to get a "classic" system-wide profile for .Net Core so I can just use CMake or whatever and not have to deal with the headache of dotnet-cli.
Re:ASP.NET Core – 2300% More Requests Served per Second by snuxoll on Thursday February 18, 2016 @06:54PM (#11130417)
I'm not even concerned about project.json because I don't particularly care for dotnet-cli, so if FSC can target .Net Core that's awesome news :)
Re:ASP.NET Core – 2300% More Requests Served per Second by KirinDave on Thursday February 18, 2016 @07:55PM (#11130714)
Would you share this process with us somewhere?
Re:ASP.NET Core – 2300% More Requests Served per Second by sremani on Thursday February 18, 2016 @06:57PM (#11130433)
CoreCLR has F# in the active ports section, but asp.net core 1.0, I do not see it, other than VB being post RTM work (in q3 2016). But, if you want to do idiomatic F#, suave.io seems to be the consensus. So things to watch for would be suave.io team using .net core 1.0 (once F# is ported to .net core 1.0) . I would not bet my farm on F# - asp.net Core1.0, anytime soon.
Re:ASP.NET Core – 2300% More Requests Served per Second by davidgrenier on Thursday February 18, 2016 @07:48PM (#11130663)
If you want to use F# it's been an awesome time since 2009, F# rocks.

I just switched from a 3 years full-time F# position to a full time PHP dev and let me tell you I'm starting to understand how much of a good time I was getting.

Re:ASP.NET Core – 2300% More Requests Served per Second by wintersFright on Thursday February 18, 2016 @08:56PM (#11130993)
Yikes. You must have missed the large sign in that career off ramp 'wrong way, go back!'!
Re:ASP.NET Core – 2300% More Requests Served per Second by egeozcan on Friday February 19, 2016 @03:46AM (#11132396)
That must have been a weird switch. Can't you use something like Haxe?
Re:ASP.NET Core – 2300% More Requests Served per Second by UK-AL on Thursday February 18, 2016 @08:32PM (#11130894)
How come you didn't just get another f# roll?
Re:ASP.NET Core – 2300% More Requests Served per Second by ZenoArrow on Friday February 19, 2016 @06:12AM (#11132847)