• RonSijm@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    They keep saying “Cloud-Native Developers” in a bunch of titles and the text, but I’m pretty sure this is mostly going to be Azure-cloud focused.

    Since AWS only supports LTS versions, a lot of things have been stuck on dotnet6 there. (Unless you install your own frameworks or docker or own ec2 images or something) - But no proper native cloud support for a lot of dotnet7 from AWS

    For example, Lambdas don’t natively support anything besides dotnet6, and dotnet8 is still scheduled to be released (Mentions February 2024, but used to mention January 2024, so who knows when it’s actually going to be released)

    Since dotnet6 and dotnet8 were LTS, I doubt dotnet9 is going to be as well, and is going to be STS again. So all the Cloud-Native stuff in dotnet9 is pretty much going to be Azure

    • Mr_Dark@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      We’ve switched to deploying everything as self-contained apps as we got tired of waiting for AWS to update their stuff.

      If Lambda cold-start is important for you, publish the app with native AOT.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        6 months ago

        If Lambda cold-start is important for you, publish the app with native AOT.

        I saw an amazing demonstration of a GUI app’s cold start time with .NET 9 AoT on Twitter: https://x.com/wieslawsoltes/status/1757488043143942528?s=20

        I don’t use AWS but I updated one of my apps (https://dnstools.ws/) to use AoT and really like it since it avoids having to deploy .NET to the servers. Saves quite a bit of disk space which is useful since this app is deployed to a bunch of small servers.