5 ms·

At first glance, it looks a lot more simple than something like ncurses. Many Linux distros are shipping .NET in the default install due to more and more apps

by skrowl 6y ago

At first glance, it looks a lot more simple than something like ncurses. Many Linux distros are shipping .NET in the default install due to more and more apps requiring it. If something like this takes off for console apps, it's only going to improve from there.

felipebueno 6y ago
I agree! With .NET Core 3.x it's possible to publish self-contained executables so there's no need to have to the runtime installed. https://docs.microsoft.com/pt-br/dotnet/core/deploying/#publish-self-contained https://docs.microsoft.com/pt-br/dotnet/core/deploying/#publ...
- colejohnson66 6y ago
  Didn’t .NET (pre-“Core”) have an AOT option? Or was that not “self-contained” (as in, a runtime was still needed prior)?
  - fuzzy2 6y ago
    Not that I know of. When you target UWP, there’s .NET Native. That might be what you’re thinking of. IIRC .NET Native compilation was very slow and could not target…, well, Windows, but only Windows UWP.
    - Iwan-Zotow 6y ago
      he's talking about ngen https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...
  - Iwan-Zotow 6y ago
    Yes, used to be called Ngen https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...
    - WorldMaker 6y ago
      Ngen was never self-contained however and ngen-ed binaries were system and runtime specific. You pretty much had to assume you couldn't ship ngen-ed binaries between machines and always ngen in place on the end user's machine. .NET Core's new AOT systems are much more capable than ngen ever was, including for static, self-contained binaries that you could potentially ship to all systems of a target architecture without shipping the non-AOT IL binaries as well. (ETA: Which is why the vast majority of .NET software hardly ever bothered with ngen except for very specific per-machine performance needs.)
      - Iwan-Zotow 6y ago
        Yes, I'm aware of that, we tried to use Ngen and basically gave up, not worth the efforts. I hope new AOT would be better
R0b0t1 6y ago
C# is a decent language, as is F#. But their success is the droves of labor contributed by MS. In some ways it is large and not easy to integrate into a distro and forms another isolated compiler base (need C# to compile C#) that is difficult to audit. Interesting is that they've adopted some of the lessons learned from Rust, or are trying to.

by skrowl 6y ago

felipebueno 6y ago

I agree! With .NET Core 3.x it's possible to publish self-contained executables so there's no need to have to the runtime installed. https://docs.microsoft.com/pt-br/dotnet/core/deploying/#publish-self-contained https://docs.microsoft.com/pt-br/dotnet/core/deploying/#publ...

colejohnson66 6y ago
Didn’t .NET (pre-“Core”) have an AOT option? Or was that not “self-contained” (as in, a runtime was still needed prior)?
- fuzzy2 6y ago
  Not that I know of. When you target UWP, there’s .NET Native. That might be what you’re thinking of. IIRC .NET Native compilation was very slow and could not target…, well, Windows, but only Windows UWP.
  - Iwan-Zotow 6y ago
    he's talking about ngen https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...
- Iwan-Zotow 6y ago
  Yes, used to be called Ngen https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...
  - WorldMaker 6y ago
    Ngen was never self-contained however and ngen-ed binaries were system and runtime specific. You pretty much had to assume you couldn't ship ngen-ed binaries between machines and always ngen in place on the end user's machine. .NET Core's new AOT systems are much more capable than ngen ever was, including for static, self-contained binaries that you could potentially ship to all systems of a target architecture without shipping the non-AOT IL binaries as well. (ETA: Which is why the vast majority of .NET software hardly ever bothered with ngen except for very specific per-machine performance needs.)
    - Iwan-Zotow 6y ago
      Yes, I'm aware of that, we tried to use Ngen and basically gave up, not worth the efforts. I hope new AOT would be better

R0b0t1 6y ago

C# is a decent language, as is F#. But their success is the droves of labor contributed by MS. In some ways it is large and not easy to integrate into a distro and forms another isolated compiler base (need C# to compile C#) that is difficult to audit. Interesting is that they've adopted some of the lessons learned from Rust, or are trying to.