3 ms·

It's not at all a closed environment though? You can live entirely on the command line if you wanted to and that's a fully supported workflow.

zoriya 3y ago
they are definitely making progress but that's clearly not the most open ecosystem. for example there is no open source debugger available (there is netcoredbg which is community maintained and lack important features or there is the vscode one which is licensed as "you need an official vscode version to use it, even vscodium can't use it")
- jwells89 3y ago
  Support for some platforms with C# is also a bit lacking. Getting C# stuff up and running on FreeBSD can be a challenge for example.
  - neonsunset 3y ago
    Do you daily drive FreeBSD?
    - jwells89 3y ago
      It’s what I run on my home server. Most of my interaction with a command line is with macOS, which makes BSDs more familiar, and jails are nice for containment that works without external tools. First class built in ZFS is nice too.
      - neonsunset 3y ago
        Quick search turns up with results to setup .NET runtime on FreeBSD without much hassle: - https://forums.freebsd.org/threads/install-net-sdk-6-7-8-on-freebsd-14.91539/ https://forums.freebsd.org/threads/install-net-sdk-6-7-8-on-... - https://www.freshports.org/lang/dotnet https://www.freshports.org/lang/dotnet And it is up-to-date, props to the maintainers! I wonder if publishing for FreeBSD without one is problematic if you use either single-file JIT (trimmed, self-contained) executables or NAOT ones. But given it's a server, such workloads generally favour JIT so it should not be an issue but I understand what you are getting at. With that said, it certainly doesn't seem to be as easy as `sudo apt-get install dotnet-sdk-8.0` but not as bad as building everything from source (which should not be too bad still, build.sh in dotnet/runtime does a lot of work for you to be able to just clone and build and the repo also has instructions for building for FreeBSD).

zoriya 3y ago

they are definitely making progress but that's clearly not the most open ecosystem. for example there is no open source debugger available (there is netcoredbg which is community maintained and lack important features or there is the vscode one which is licensed as "you need an official vscode version to use it, even vscodium can't use it")

jwells89 3y ago
Support for some platforms with C# is also a bit lacking. Getting C# stuff up and running on FreeBSD can be a challenge for example.
- neonsunset 3y ago
  Do you daily drive FreeBSD?
  - jwells89 3y ago
    It’s what I run on my home server. Most of my interaction with a command line is with macOS, which makes BSDs more familiar, and jails are nice for containment that works without external tools. First class built in ZFS is nice too.
    - neonsunset 3y ago
      Quick search turns up with results to setup .NET runtime on FreeBSD without much hassle: - https://forums.freebsd.org/threads/install-net-sdk-6-7-8-on-freebsd-14.91539/ https://forums.freebsd.org/threads/install-net-sdk-6-7-8-on-... - https://www.freshports.org/lang/dotnet https://www.freshports.org/lang/dotnet And it is up-to-date, props to the maintainers! I wonder if publishing for FreeBSD without one is problematic if you use either single-file JIT (trimmed, self-contained) executables or NAOT ones. But given it's a server, such workloads generally favour JIT so it should not be an issue but I understand what you are getting at. With that said, it certainly doesn't seem to be as easy as `sudo apt-get install dotnet-sdk-8.0` but not as bad as building everything from source (which should not be too bad still, build.sh in dotnet/runtime does a lot of work for you to be able to just clone and build and the repo also has instructions for building for FreeBSD).