Live data from Hacker News

.NET 8

devblogs.microsoft.com

231–240 of 374 posts

Re: .NET 8

#231

Earlier quoted context omitted.

Maybe it has gotten better. I found it way too much, but then I am writing Python in Notepad++. All I saw was far too many options and an assumption that you were Writing At Enterprise Scale.

If it was a whole decade ago it's hard to state how much the ecosystem has changed since then. Since 2014 they've released Community Editions of Visual Studio, with a lot more useful features and less restrictive licensing than the old Express editions. But if you're used to writing Python in Notepad++ I'd skip VS entirely. You can install the dotnet SDK and just keep using Notepad++. Here's literally everything to w…

Is there a book you would recommend that targets small-scale usage like mine? A CLI, a GUI, or maybe a Windows Service that fires off every so often.

I have noticed someone in a previous job who wrote an application that somehow tied itself to IIS despite not having any web site needed as a front end and found that somewhere between baffling (was there something I just wasn't getting? Is this how things are done now?) and intimidating (wow, that's a lot of infrastructure for something so small).

I'm looking for something which might target the IDE and little tips like the you have helpfully included.

Re: .NET 8

#232

Adding spreading is neat, but curious why they chose to go the two dot route instead of three. It's been a while since I've worked in C#, so I can't remember if there are any reserved implications of three dots.

Hi there. I'm the language designer who created the 'Collection Expression' design/specification: https://github.com/dotnet/csharplang/issues/5354 You can see the entire history of the proposal there. To answer you specific question, we went with `..` because that's what the language already uses for the complimentary 'pattern matching deconstruction' form for collection patterns. In other words, you can already say…

A general offtopic comment, but something that confused me when I was looking at the github issues and docs for the spread operator.

I've noticed that `...` is frequently used to denote that there's some code that's omitted. However with the spread operator being added (and being `...` in other languages) and "we also felt like it might be an operator we might want to use in the future for other language features" it's a bit confusing at a glance whether that's new syntax or just a shorthand. And it makes searching difficult.

I'm not sure what to replace it with, possibly a comment would be clearer: `/* code here */` or at least `/* ... */`.

P.S. Collection expressions are an awesome new addition!

Re: .NET 8

#233

Earlier quoted context omitted.

What is the issue with using Visual Studio Community Edition? Or if not on Windows, using VS Code with the plugin. All free.

Visual Studio for Mac is discontinued and will be retired next year: https://learn.microsoft.com/en-us/visualstudio/mac/what-happ...

Right. They rewrote the .NET plugin for VSCode as a replacement. It's reasonable.

Re: .NET 8

#234
post #51

Earlier quoted context omitted.

Big difference is that Go is stable and conservative, net core keep adding a billion features every release. Looking at some net core 2/3 stuff and now to see how many things changed. Good luck with your code base in 5 years when someone decide to add all the new stuff.

I don't know Go that much, but the part about .Net is so untrue. First, C# was published in 2001, while Go was released in 2009. So there's 8 years of "more stuff". Also (see in comments too), upgrading .Net is very easy. There are man not-to-small codebases can be "easily" upgraded from .Net Core 3 to 8 without any hassle. Backwards comptability was always baked into Microsofts thinking. .Net 7 and 8 did also (IMHO)…

Do you want to compare the number of features added between go and c# in the last 15 years? Just a single major release of C# added more stuff than probably the last 15 years of Go.

I'm not saying Go is 100% right in that, but it's much more conservative about stuff added into the language.

Re: .NET 8

#235

Earlier quoted context omitted.

What is the issue with using Visual Studio Community Edition? Or if not on Windows, using VS Code with the plugin. All free.

Wasn’t there some issue with debugger on Non-Windows platforms?

The issue that it is free as in beer but not open source as in MIT.

Re: .NET 8

#236
post #44

Earlier quoted context omitted.

- It is a mature platform with yearly updates. - New stuffs integrate nicely with existing features. - C# and F# gets yearly updates. - Somehow they manage to get the platform faster every year. - Microsoft Orleans.

Microsoft seems weird tho. They dont really support any recommended way to do .NET on Mac and you have to rely on Rider or half ass VS Code experience.

[deleted]

Re: .NET 8

#237
post #44

Earlier quoted context omitted.

- It is a mature platform with yearly updates. - New stuffs integrate nicely with existing features. - C# and F# gets yearly updates. - Somehow they manage to get the platform faster every year. - Microsoft Orleans.

Microsoft seems weird tho. They dont really support any recommended way to do .NET on Mac and you have to rely on Rider or half ass VS Code experience.

Rider is so much better than Visual Studio or Code in my opinion, but I understand how the price could be a deal breaker.

Re: .NET 8

#238

Earlier quoted context omitted.

.NET / C# seems to be following C++ by including... everything. I wonder if they're just not worried about feature bloat or what's their thinking...

Hi there, C# Lang Designer here. :) We're always thinking about the bloat concern when it comes to language development. However, our philosophy on it is that bloat primarily comes when you add replacement systems that are expected to supersede the previous mechanisms, not compliment them. So we try to do the former sparingly . In the history of C# there are very few times we've actually done this, and we do view tho…

The new array literals seem to supersede some previous syntaxes like new[] { 1, 2, 3 } goes to [1, 2, 3] in a lot of cases. But overall they are a _great_ addition to the language playing around with them now so bravo.

Still not really sure how I feel about class primary constructors on the other hand, will give them some time to marinate.

Re: .NET 8

#239

Earlier quoted context omitted.

Visual Studio for Mac is discontinued and will be retired next year: https://learn.microsoft.com/en-us/visualstudio/mac/what-happ...

Right. They rewrote the .NET plugin for VSCode as a replacement. It's reasonable.

Well, the C# DevKit has to fix quite some bugs. I love it but it needs more work.

Re: .NET 8

#240

Lots of very cool stuff here (AOT, Aspire, etc.). .NET has been held down by the image of its early days, but it has become a pure joy to work with recently. The improvements in tooling and ergonomics have made it a replacement for Go in our org (we migrated from .NET Core 3.1 to Go back to .NET 6 recently).

> .NET has been held down by the image of its early days, but it has become a pure joy to work with recently People have been saying that for the past 4 years. As someone who's never used .NET but develops embedded apps for Linux, I had high hopes for it become the best story for crossplatform development, it still feels like the crossplatform is held by ductape. It's still Xamarin for mobile, Avalonia (a 1-man proje…

I would love that they support a framebuffer (rendered controls) or Linux native control rendering in Maui for exactly that reason. But no, QT continues it's painful reign.
Post reply on HN