Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET 6 Released

devblogs.microsoft.com

Post reply on HN
Print view View original

411–420 of 428 posts

Re: .NET 6 Released

#411

Post by JohnTHaller »

mrweasel wrote: post #168
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

If it's like v5, you can. They're big (since they include .NET, though it looks like v6 will strip out more than v5). And they won't run on Windows 7 without an administrator installing a system component first.

Re: .NET 6 Released

#412

Post by azinman2 »

rbanffy wrote: post #382
azinman2 wrote: post #287

Earlier quoted context omitted.

Not to mention they behave differently with respect to HiDPI.

Remember how much criticism Linux and other unixes got by people complaining about apps created with KDE on Gnome desktops and vice versa? I'll never forget ;-)

And that’s a disaster too.

Really the only one that’s done it correctly is Apple.

Re: .NET 6 Released

#413

Post by int_19h »

azinman2 wrote: post #412
rbanffy wrote: post #382

Earlier quoted context omitted.

Remember how much criticism Linux and other unixes got by people complaining about apps created with KDE on Gnome desktops and vice versa? I'll never forget ;-)

And that’s a disaster too. Really the only one that’s done it correctly is Apple.

Apple also did this whole "our apps are special" thing more than once.

I don't know why, but there's this weird temptation for every app to try to present itself as some kind of unique work of art, when it comes to UX. But I don't want art, and I don't want branding. I just want ergonomic tools - and part of ergonomics is not to have to re-learn everything every time you pick up a new thing.

Re: .NET 6 Released

#414

Post by mmgutz »

DeathArrow wrote: post #365
mmgutz wrote: post #284

Earlier quoted context omitted.

Don't think it's just about coolness. In .NET there is usually one way to do things, the MS way. You don't have options. Whatever MS prescribes is practiced by most enterprise shops. I remember arguing for something closer to MVC (several open source solutions) when ASP.NET forms was the way to do things. It wasn't until ASP.NET MVC came out that enterprise shops came on board. I still see a lot of documentation that…

>In .NET there is usually one way to do things, There are infinite ways to do things. But the most easier way to do things is one. And that is good because anyone can understand anyone's code.

There are many languages that are easier to follow than C#. Every import in Go or Node is explicit. You don't need an IDE to tell you which package a method originates from.

Anyway, my point is there are very legitimate reasons why most startups don't use .NET. And it rarely has anything to do with being cool.

Re: .NET 6 Released

#415

Post by 0xfeeddeadbeef »

kreeben wrote: post #4

>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.

Historically — yes, ASP.NET Core 1 and 2 had the ability to live _inside_ both .NET Framework and .NET Core.

Re: .NET 6 Released

#416

Post by AtNightWeCode »

loic-sharma wrote: post #316
AtNightWeCode wrote: post #74

Earlier quoted context omitted.

I never run anything else than LTS in production. The in-between versions have basically been beta quality since .NET 1-preview.

Disclaimer: I work on .NET What makes you say that? All versions of .NET - including non-LTS versions - have had an extremely high bar for quality before releasing.

I worked with all .NET versions. The most none-code related .NET bugs I had to hunt down in modern time has been in .NET Core 1.0 (clear leader) and .NET Core 2.2. The thing I like about the LTS versions is that they always work in and with any part of the ecosystem. Actually, one of our clients had to downgrade from .NET 5.

Re: .NET 6 Released

#417

Post by icey »

magicalhippo wrote: post #94
kbd wrote: post #51

Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…

> I certainly wouldn't feel comfortable to say to my team "let's do this next project in C#". Could you expand a bit on that? I used .Net 1.1 and 2.0 for awhile, and coming back to it now while deciding the future path for our application.

I left .net around the 2.0 days and came back with .net core 5.0. It's a world of difference, and absolutely worth checking out again. If anything, you don't need Windows to run it, and there's great tooling support outside of Visual Studio (VS is still pretty nice though).

Re: .NET 6 Released

#418

Post by oaiey »

cutler wrote: post #369
oaiey wrote: post #231

Earlier quoted context omitted.

Legacy exists in every company and platform older than some years. You either do the business of brownfield jobs or not. Every platform has their ugly history .. they just call them differently: SOAP/WS, RMI, CORBA, 2to3, PHP4, jQuery, AngularJS 1, ... . If a platform does not have history, I would be worried that I am riding something which soon is the legacy. Microsoft does not play catchup in the web space. It is…

Any idea why .Net rates seem to be significantly lower than for comparable Java roles? Seems to be true in the UK according to Indeed.

That is market specific. Cannot answer for the UK.

Re: .NET 6 Released

#419

Post by to11mtm »

chadcmulligan wrote: post #386
to11mtm wrote: post #222

Earlier quoted context omitted.

In all fairness, at one point you could actually make sense of things. Unless I'm misremembering, until recently Avalonia was still being touted as primarily a replacement for Desktop WPF. I was shocked to see they're talking about mobile now too. I guess it's somewhat expected. Uno basically does what MAUI does. The main difference being, Uno has been around for a while longer and something you've been able to use f…

> - Click new project - Fill out the form - Get a Design window, - Drag a 'Textbox' into the design window, - Drag a 'Button' into the design window, - Double click on the button, get taken into a generated event handler, and the user can intuitively put in the right code (i.e. updating the viewmodel with 'hello world'.) - Click 'run' Its been a while since I looked at these and I was having a look for a designer lik…

When I played with Uno, There was a UWP designer (At the time Uno relied on UWP for the API/Translation, IDK if that's changed.) It worked mostly like the WPF designer but I think it was slightly more limited.

Re: .NET 6 Released

#420

Post by to11mtm »

naasking wrote: post #394
to11mtm wrote: post #222

Earlier quoted context omitted.

In all fairness, at one point you could actually make sense of things. Unless I'm misremembering, until recently Avalonia was still being touted as primarily a replacement for Desktop WPF. I was shocked to see they're talking about mobile now too. I guess it's somewhat expected. Uno basically does what MAUI does. The main difference being, Uno has been around for a while longer and something you've been able to use f…

> - Click new project - Fill out the form - Get a Design window - Drag a 'Textbox' into the design window, - Drag a 'Button' into the design window Non-starter these days. Building a form graphically doesn't take into account multiple screen sizes and screens that can change dimensions on the fly, which are now far more prevalent than the heady desktop UI days that you're talking about here. Unless you have some nove…

> Non-starter these days.

It's about the species; Remember that I mentioned that in the context of 'someone getting started'. I say what I say because it would be the best thing to help new users get 'hooked,' not necessarily because it's the best way to make a maintainable app. (IDK though, some of my one-team winforms stuff was actively maintained for years after I left)

> Building a form graphically doesn't take into account multiple screen sizes and screens that can change dimensions on the fly, which are now far more prevalent than the heady desktop UI days that you're talking about here.

There's no reason you couldn't handle such a thing in WPF. Sure, it may be more -work- to check representation in both formats, and some form of helper (that would handle certain scaling factors of buttons/etc) would be a boon to developers. That's not the way I look at it though, see below;

> Unless you have some novel idea for how to design graphically for all sorts of screen sizes.

It's not necessarily about making a 'single' UI that works on both mobile and Desktop. If you can even get to the point where a user can make separate Mobile -and- Desktop 'form-style' built screens for their app, all in one happy framework/language... Frankly that would be the best thing overall, since you can provide optimized Desktop -and- Mobile UIs, and not have to have a bunch of disparate technologies used to build each.

Post reply on HN