.NET 6 Released • Hacker News Board

Re: .NET 6 Released

#161

Post by solarkraft » Mon, Nov 08, 2021, 8:20 PM UTC

runevault wrote: post #20

Been thinking about switching to Rider (already had the personal license for Jetbrains from wanting CLion for Rust) and figured .NET 6 would be a good time to try making the switch. With how blah VS has been for a while hopefully I'll like the Rider experience better (for both c# and f#) Edit: Though I saw something this morning when I tried to load an f# project I made in VS refused to load even though the new ones…

+1 for Rider. It’s one of the 2 .NET IDEs I know that don’t suck terribly (the other being the proprietary version of VSCode).

Re: .NET 6 Released

#162

Post by azth » Mon, Nov 08, 2021, 8:21 PM UTC

vb6sp6 wrote: post #119

azth wrote: post #114

Earlier quoted context omitted.

You should also be able to do this in Java with jlink.

yes but then you have to write your program in java

Yes, arguably a better decision than writing it in golang to begin with.

Re: .NET 6 Released

#163

Post by Thaxll » Mon, Nov 08, 2021, 8:23 PM UTC

abdusco wrote: post #135

polskibus wrote: post #129

Earlier quoted context omitted.

What do you mean by golang quirks?

No passable debugger, weird typing system, verbose error handling, lack of exceptions, generics, syntactic sugar ... I'm a novice at Golang, and I dislike much of the language, except that it's fast and can produce small binaries.

"verbose error handling, lack of exceptions"

Exactly why I prefer Go to Java and C#.

Re: .NET 6 Released

#164

Post by solarkraft » Mon, Nov 08, 2021, 8:24 PM UTC

jekude wrote: post #34

As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?

History. Microsoft technology used to suck terribly for small-time developers. It was always popular in the “enterprise” (which also brings with it some extra architectural baggage), but if you wanted to ship an app with it to consumers you basically couldn’t ... until Xamarin, Mono and dotnet core.

Re: .NET 6 Released

#165

Post by WorldMaker » Mon, Nov 08, 2021, 8:27 PM UTC

foepys wrote: post #149

WorldMaker wrote: post #140

Earlier quoted context omitted.

Yeah, hopefully as others have pointed out, with .NET 7 next year all the version numbers align so that ASP.NET and EF can drop "Core" again.

Searching the internet for help is going to be a nightmare, though.

Shouldn't be too bad, I don't think, if you remember the version number. Which anyone that worked in ASP.NET 4, 5 or 6 was generally pretty used to (a lot of things changed between versions even the "classic" .NET Framework days). I still have "fond" memories of fighting to find a specific EF6 answer that was different from EF4 or EF5, but that was still somewhat easier than having to remember to add "core" to all your searches lest you get classic EF3 results when searching for EF Core 3.x help. Having a version number high enough that you no longer need "core" is something I'm looking forward to.

Re: .NET 6 Released

#166

Post by solarkraft » Mon, Nov 08, 2021, 8:28 PM UTC

adamredwoods wrote: post #64

jekude wrote: post #34

As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?

The package manager is not the best, it may have improved since last I used it. Also .Net really needs Visual Studio (not VS Code) to unlock its full potential.

VS holds .NET back, IMO. VScode (proprietary version) is less powerful (especially on the refactoring side), but does have a bunch of nice features.

Rider is the perfect replacement, though. Comes with all the features of ReSharper (this is a big deal for many .NET workflows, VS may have integrated many of its features, but not all of them) and extensions and themes you can actually use (IME with VS of the 50% that promise to do what I want 90% are broken).

JetBrains just know what they’re doing. They’re clearly prioritizing quality (something the VS team seems to be actively working against).

Oh, and it’s damn near 100% compatible with VS projects (one thing I missed about 2 years ago were live updates of WPF XAML, everything else just worked).

Re: .NET 6 Released

#167

Post by dsizzle » Mon, Nov 08, 2021, 8:30 PM UTC

abdusco wrote: post #24

> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories. This is a great! Now I can publish statically linked executables and run it e…

Kind of curious that Microsoft had a feature that was available in Linux but not Windows, no?

Re: .NET 6 Released

#168

Post by mrweasel » Mon, Nov 08, 2021, 8:32 PM UTC

abdusco wrote: post #24

> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories. This is a great! Now I can publish statically linked executables and run it e…

Wait, wait… .Net can build “static linked” executables that doesn’t require that I install .Net to run? I had no idea, I guess it’s time to revisit .Net

Re: .NET 6 Released

#169

Post by svick » Mon, Nov 08, 2021, 8:38 PM UTC

kingcharles wrote: post #97

sedatk wrote: post #29

Earlier quoted context omitted.

The whole runtime gets included in the binary.

This actually makes sense in 2021 since we have the resources to allow things like this. 20 years ago this might have seemed insane.

Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime.

Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.

Re: .NET 6 Released

#170

Post by exyi » Mon, Nov 08, 2021, 8:40 PM UTC

dsizzle wrote: post #167

abdusco wrote: post #24

> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories. This is a great! Now I can publish statically linked executables and run it e…

Kind of curious that Microsoft had a feature that was available in Linux but not Windows, no?

Yea, funny :D However, the problem was mostly deploying dotnet apps on servers which did not have dotnet installed. Windows has .NET installed anyway, so there the problem did not really exist