<story><title>Exploring the .NET Core Runtime</title><url>http://www.mattwarren.org/2018/12/13/Exploring-the-.NET-Core-Runtime/</url></story><parent_chain><item><author>eksemplar</author><text>Do people really use .NET core, and if so, why?&lt;p&gt;We’ve been a C# house for several years, decades really, and I’ve always preferred it to JAVA so I’m actually excited for Core.&lt;p&gt;But we rarely use it. Not because it’s not great, rather because we’re more productive with flask or Django. For Core to really make sense for us, it’d would have to stop being so damn low level, but I guess that maybe it can’t without sacrificing too much efficiency. More importantly it needs better libraries for things that aren’t “built-in”.&lt;p&gt;I can certainly see why .NET developers welcome it, because they finally have good cross platform ability. At least until they need to do authentication on a non-standard SAML token, that though easily supported by ADFS but is a bitch in any .NET setup.&lt;p&gt;I know we aren’t most use cases, being the public sector and running a gazillion different tech stacks at once, but .NET has never played well once you stepped outside it’s comfortzone and it’s always been so low level that writing library extensions were a bitch. And that may have worked out, so far, but I just don’t see why people stick with it when there are more productive alternatives.&lt;p&gt;I say productive, because I don’t think .NET core is lacking technically, but delivering solutions on time and with minimum maintenance requirements afterward is just easier in python or JAVA and I’d imagine others as well.&lt;p&gt;But maybe I’m missing something?</text></item></parent_chain><comment><author>romanovcode</author><text>Using .NET Core on production here.&lt;p&gt;&amp;gt; but delivering solutions on time and with minimum maintenance requirements afterward is just easier in python or JAVA&lt;p&gt;I would agree if you would replace Python&amp;#x2F;Java with Node, but with these languages I don&amp;#x27;t see it.&lt;p&gt;&amp;gt; on time and with minimum maintenance requirements afterward&lt;p&gt;This is my Dockerfile, it is serving me without changes (technically replacing 2.1 with 2.2 is a change) for more than 6 months.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    # Build assets
    FROM node:8-alpine AS assets
    WORKDIR &amp;#x2F;app
    COPY src&amp;#x2F;Website&amp;#x2F;Package.json .&amp;#x2F;Website&amp;#x2F;package.json
    COPY src&amp;#x2F;Website&amp;#x2F;Gulpfile.js .&amp;#x2F;Website&amp;#x2F;
    COPY src&amp;#x2F;Website&amp;#x2F;Static&amp;#x2F;. .&amp;#x2F;Website&amp;#x2F;Static
    WORKDIR &amp;#x2F;app&amp;#x2F;Website
    RUN npm install
    RUN npm run build

    # Build project
    FROM microsoft&amp;#x2F;dotnet:2.2-sdk-alpine AS build
    WORKDIR &amp;#x2F;app
    COPY src&amp;#x2F;Website&amp;#x2F;*.csproj .&amp;#x2F;Website&amp;#x2F;
    WORKDIR &amp;#x2F;app&amp;#x2F;Website
    RUN dotnet restore
    WORKDIR &amp;#x2F;app
    COPY src&amp;#x2F;Website&amp;#x2F;. .&amp;#x2F;Website&amp;#x2F;
    WORKDIR &amp;#x2F;app&amp;#x2F;Website
    RUN dotnet publish -c Release -o dist

    # Run project
    FROM microsoft&amp;#x2F;dotnet:2.2-aspnetcore-runtime-alpine AS runtime
    WORKDIR &amp;#x2F;app
    COPY --from=build &amp;#x2F;app&amp;#x2F;Website&amp;#x2F;dist .&amp;#x2F;
    COPY --from=assets &amp;#x2F;app&amp;#x2F;Website&amp;#x2F;Static&amp;#x2F;dist .&amp;#x2F;Static&amp;#x2F;dist
    RUN rm &amp;#x2F;app&amp;#x2F;Data&amp;#x2F;Log&amp;#x2F;.gitkeep

    ENTRYPOINT [&amp;quot;dotnet&amp;quot;, &amp;quot;Website.dll&amp;quot;]

&lt;/code&gt;&lt;/pre&gt;
&amp;gt;But maybe I’m missing something?&lt;p&gt;I think you might be.</text></comment>
<story><title>Exploring the .NET Core Runtime</title><url>http://www.mattwarren.org/2018/12/13/Exploring-the-.NET-Core-Runtime/</url></story><parent_chain><item><author>eksemplar</author><text>Do people really use .NET core, and if so, why?&lt;p&gt;We’ve been a C# house for several years, decades really, and I’ve always preferred it to JAVA so I’m actually excited for Core.&lt;p&gt;But we rarely use it. Not because it’s not great, rather because we’re more productive with flask or Django. For Core to really make sense for us, it’d would have to stop being so damn low level, but I guess that maybe it can’t without sacrificing too much efficiency. More importantly it needs better libraries for things that aren’t “built-in”.&lt;p&gt;I can certainly see why .NET developers welcome it, because they finally have good cross platform ability. At least until they need to do authentication on a non-standard SAML token, that though easily supported by ADFS but is a bitch in any .NET setup.&lt;p&gt;I know we aren’t most use cases, being the public sector and running a gazillion different tech stacks at once, but .NET has never played well once you stepped outside it’s comfortzone and it’s always been so low level that writing library extensions were a bitch. And that may have worked out, so far, but I just don’t see why people stick with it when there are more productive alternatives.&lt;p&gt;I say productive, because I don’t think .NET core is lacking technically, but delivering solutions on time and with minimum maintenance requirements afterward is just easier in python or JAVA and I’d imagine others as well.&lt;p&gt;But maybe I’m missing something?</text></item></parent_chain><comment><author>kungito</author><text>I&amp;#x27;ve worked in many languages including C#, Python,Javascript, Typescript, Haskell and while I understand Python and Javascript are amazing for prototyping, I don&amp;#x27;t see the advantage in the &amp;quot;on time with minimum maintenance&amp;quot; which Python has against C#.&lt;p&gt;Could you please expand on this one?</text></comment>