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

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

321–327 of 327 posts

Re: Announcing .NET Core 1.0

#321

Post by ubertaco »

enricosada wrote: post #243
Eyas wrote: post #209

Earlier quoted context omitted.

I don't think so. It means that the tooling is broken, which is not at 1.0 yet (still in `preview2` I believe).

Exacly, the preview2 of the sdk, atm, is broken for f#. Not the .net core, that's ok. new console/lib templates are going to be published (with the fixed fsharp compiler/library package), that's all.

Still a little odd for a release announcement. It feels disingenuous to only afterwards make the fine-grained distinction that yes the libraries are technically v1, but the tooling is still in preview.

Kinda like announcing your new line of cars is ready for purchase today! Except that down in the fine print you might find out that the engine is ready to go, but the steering wheel, headlights, dashboard, and pedals are all still in development and so it's justifiable that they're broken.

Re: Announcing .NET Core 1.0

#322

Post by arthursilva »

igouy wrote: post #307
arthursilva wrote: post #293

Earlier quoted context omitted.

I find the binary-tree benchmark specially disturbing, it looks like the .NET Core GC/escape-analysis has some catching up to do.

The multi core difference? Check the cpu secs and cpu load; check the source code.

Oh I should have checked that first. Thanks.

Re: Announcing .NET Core 1.0

#323

Post by enricosada »

ubertaco wrote: post #321
enricosada wrote: post #243

Earlier quoted context omitted.

Exacly, the preview2 of the sdk, atm, is broken for f#. Not the .net core, that's ok. new console/lib templates are going to be published (with the fixed fsharp compiler/library package), that's all.

Still a little odd for a release announcement. It feels disingenuous to only afterwards make the fine-grained distinction that yes the libraries are technically v1, but the tooling is still in preview. Kinda like announcing your new line of cars is ready for purchase today! Except that down in the fine print you might find out that the engine is ready to go, but the steering wheel, headlights, dashboard, and pedals a…

Was like that also in the previous release. The .net core was rc2 and the .net core sdk was preview1.

I use it, and i think it's ok. The sdk it's just a build system. the real value is the .NET Core, that mean the coreclr (the virtual machine) and the foundation libraries (corefx). I can change the build system one month from now, to build a project using the old packages.

It's not a car (engine vs wheel). It's more like food vs marketplace. the food it's the real deal, the markeplace may be incomplete (no parking).

Re: Announcing .NET Core 1.0

#324

Post by runT1ME »

aphextron wrote: post #277
runT1ME wrote: post #241

Earlier quoted context omitted.

On top of that, Scala is a much nicer language than C#. I moved from being a C# developer to Scala and couldn't be happier. Best thing about C# is Visual Studio (IDEs are weaker in Scala land) but a bigger ecosystem and more powerful language make it for it imo.

Could you sell me on Scala over C#?

Pattern Matching, Destructing, and ADTs are amazing. Inference is much better and not just for local variables.

for comprehension is the equivalent of LINQ syntax which is nice, very powerful when working with asynchronous calls.

Higher Kinded Types combined with implicit parameters are the two aces in the hole that make it an asbolute definitive win when heads up against C#. When I had to switch back to C# in my last job (some projects were scala, some C#) this was what I missed the omst. Combining the two gives you the 'type class pattern', which is pretty much the first time i've actually seen composition and code sharing just work without the cruft of an 'OO' like framework.

http://www.cakesolutions.net/teamblogs/demystifying-implicit...

Re: Announcing .NET Core 1.0

#325

Post by hackaflocka »

oblio wrote: post #319
hackaflocka wrote: post #315

Earlier quoted context omitted.

Thanks. Very helpful. Last 2 Qs: is Framework different from Core? And how does Windows Presentation Foundation fit in all this?

.NET Framework is the old .NET Framework. It's basically the entire shebang, tied to Windows: VM, class libraries, etc. .NET Core is as the name says, just the "core" of the .NET Framework, the part that's cross platform. However, I'm not sure that at this point the code's common, I believe at least a part of it has been reimplemented. I think that in the future .NET Framework will be based on .NET Core. Therefore .N…

Thanks. That clarified everything. Sad that one can't find this simplified info on Wikipedia or on the Microsoft website.

Re: Announcing .NET Core 1.0

#326

Post by emn13 »

cfreeman wrote: post #242
BHSPitMonkey wrote: post #208

Earlier quoted context omitted.

Well, it would be nice if there is a way to vote or express one's needs via some alternative to having one's usage actively mined for data.

I think you are truly in a minority if you'd rather take a survey than have the data collected automatically. There has to be a sane middle ground.

Data collected by a neutral third party without conflicting interests pushing for creative monetization opportunities that's responsible for sufficient annonymisation/aggregation before releasing the data?

Re: Announcing .NET Core 1.0

#327

Post by jsingleton »

jsingleton wrote: post #110
dewiz wrote: post #102

Earlier quoted context omitted.

You're missing akka.net there

Thanks! I have a big list of things to add but I'll check this is on there and add it if they are planning (or have already added) support for Core. It started as things I had talked about in my recent book.

Added, closing https://github.com/jpsingleton/ANCLAFS/issues/4, thanks!
Post reply on HN