It's so bad. It's unfortunate because it's otherwise a pretty great keyboard; I'd love something similar with an Fn row.
1,572 karma · joined April 24, 2015
It's so bad. It's unfortunate because it's otherwise a pretty great keyboard; I'd love something similar with an Fn row.
There's more detail in the official C# docs: https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...
And in the GitHub issue for the feature: https://github.com/dotnet/csharplang/issues/287
Mistyping the parameter name results in the following compiler warning, thankfully:
CS8963 The CallerArgumentExpressionAttribute applied to parameter 'conditionExpression' will have no effect. It is applied with an invalid parameter name.
https://github.com/chromelyapps/Chromely https://github.com/webview2/EdgeSharp
Not the impression I got after the hot reload disaster. I'm the person who raised the initial GitHub issue, and I talked to a handful of people high up in DevDiv off-the-record at the time.
People were very unhappy with the decision internally, concerns were raised, and she still went ahead with a decision that showed very poor judgment.
Yup. Office tried MSIX for a little while and then gave up because it broke many things, including the software I work on professionally. It's a mess.
It's poorly documented and unreliable compared to tried-and-true installation mechanisms like MSI and Inno Setup. I've had MSIX installations fail on nearly-fresh Windows 10 installs with zero useful information presented to the user or logged in the event log.
Don't even get me started on the registry+filesystem virtualization; I've seen it cause bugs in multiple first-party applications when they're installed via the Store.
I think this is the right call on Microsoft's part. UWP has been semi-abandoned for a while now and it's nice to get some clarity on its future (or lack thereof).
UWP had many pain points (the .NET Native compiler, installation, filesystem access, sandboxing, longstanding XAML limitations), but it wasn't all bad. You can tell that the Windows team spent a lot of effort trying to make UWP/WinRT/WinUI successful, and it's a little sad that most developers never got to see the good parts of UWP. Among other things, UWP made it remarkably easy to build interfaces that "just work" with both touch input and keyboard+mouse.
It's unfortunate that UWP was hobbled from the start with so many restrictions. I think it would have seen much more adoption if it had been built with an escape hatch from the draconian distribution+sandboxing requirements.
Rider’s implemented hot reload on their own, so this isn’t helping against Visual Studio’s main commercial competition.
If .NET is going to stay relevant in the long run, it needs a better reputation for cross-platform development and much better tooling outside of Visual Studio. Newcomers to the language expect it to work well in VS Code, and they are frequently disappointed.
This decision moves .NET backward in areas it already needs to do better in, and to add insult to injury it does so by deleting already-working code.
I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple platforms and technologies. I've built my own hooks into the hot reload feature, and I've used it to get a tight feedback loop in many different kinds of applications. It's awesome.
I was so excited to be able to point to that feature and say "yes, .NET has a great developer experience - even outside Visual Studio". I haven't always been able to do that. And now... it's going away as a broadly available feature, so that some bean counter can use it to drive usage of a legacy IDE (I love Visual Studio, but let's not kid ourselves about where the future lies).
Immediate feedback (i.e. a fast inner loop) isn't a niche feature - it's an essential element of any creative activity (see: Bret Victor). They are crippling .NET and it hurts to see it.
Just remember that there’s a huge number of people who appreciate the work you’re doing to modernize terminal experiences on Windows (nearly 78k GitHub stars!)
I'm not aware of any public plans to move VS Code to WebView2, but I would be surprised if it doesn't happen eventually.
Between hot reload and the improvements to make C# simpler and less verbose, I'm really excited for this release.
I am really looking forward to the day when I can use C# for all my scripting needs instead of Bash/Python/PowerShell. We’re getting there.