1. 5
  1.  

  2. 2

    It feels like just yesterday the project was announced! Props to the Microsoft for reaching a great and stable iteration* so quickly!

    *cross-platform near-complete rewrite

    1. 0

      I dunno, call me a cynic, but it only adds support for Linux which they have been flirting with as a company for the last few years. If it was written half even half decently this shouldn’t have been too much work. Apart from open sourcing it (which is appreciated) they haven’t really done anything they weren’t going to do anyway. If they port or accept patches to port it to Mac that would be slightly more interesting as it is outside their apparent game plan.

      1. 2

        It already does run on mac (officially). Unsure about all of .NET Core, but CoreCLR runs on FreeBSD and NetBSD as well (although I don’t believe those ports have the same level of support as on macOS/Linux/Windows).

        1. 1

          There were a huge swathe of api changes that everybody seems to really appreciate and wouldn’t have happened without community input. The api is very very very different for the .net core libs but in terms of the clr itself, I believe it’s a port.

          1. 1

            Do you have a few examples? Would really love to see what they changed. The last time I played with .NET the API design felt like overloading-from-hell.

            1. 1

              They unified MVC and Web API stuff so Json-batteries are included, it’s easier to return responses that aren’t just View(), a lot of framework stuff got moved from being class parameters to interface parameters, configuring your application at startup is a lot less unwieldy, there’s now built-in dependency injection (although dependency injection’s always put a bad taste in my mouth, autofac is very popular in the c# world), MTest is replaced with xUnit.net, better decoupling from IIS (kestrel is the http server used outside of Windows), tag helpers are a new thing, so you can use special attributes on your markup to add behavior instead of inlining a lot of razor markup, and nuget package management is way simpler

              Disclaimer for you: the mvc/net apis are still very very mvc/net-y. The changes made are (imo) mostly just updating practices in the framework to align with practices of developers using it.

      2. 2

        This is pretty cool; I wish it was brew install-able but otherwise I’m stoked to poke around and see how it works.

        1. 1

          Damn it, mangled the link when pasting. Can a mod fix it please?

          1. 1

            Should work now.