At work we have a custom disposable data provider that gets into trouble if you use async/await inside it.

Traditionally this was enforced through oral history, but with agents this needed addressing.

It was actually really easy to write a custom analyzer which can pick up whether `await` is ever called within the scope of this provider and fail the compilation.

The only thing you have to be careful of, is making sure the LLM doesn't sneak in some "ignore Rule CUST001" pragma blocks, but it's mostly good about not doing that, unless it thinks you're "prototyping", in which case it seems to treat errors as inconveniences to be worked-around.

Certainly it doesn't feel any easier to manage multiple windows than when we had a quarter of the screen space.

System.Text.Json is part of the core standard library, the only reason to use Newtonsoft is developing on legacy applications.

Visual Studio isn't necessary or even much recommended any more. VSCode or any LSP editor works fine.

You don't need to install nuget, any more than you need to install cargo in rust, it's part of the SDK. You can also just edit the csproj in the same way you could edit your TOML file. It's XML, and you just add .

You can compile --self-contained to be able to run it somewhere without the runtime installed.

.NET has a long history, but almost none of these are actual points of friction in the current year.

If it's "Large standard library", I think that's a selling point. Having anything you need available ( although these days, via optional microsoft.* packages ) helps keep projects consistent between different places.

If it means "Different ways to do the same thing", I can understand that criticism better, and some of that comes with 20+ years of legacy, where the wrong thing was done, and now there's a better way, but a ruthless adherence to backward compatibility means that the old way isn't dropped.

.NET has almost all these upsides, but with a concurrency model (async/await) that is (now) more transferable to other languages.

We seem to have lost the war for people to find their own voice, the AI articles are getting widely upvoted, and people pointing out they are AI are no longer getting traction, people don't seem to care.

Except you can, because there's a greyed out but functional "necessary cookies only" button, but only after clicking customise.

At some point there needs to be a reckoning for companies that take the piss like this.

You could substitute the word knitting for almost any hobby, and the article would read almost the same.

It's an article about the soulless content-free world of AI podcasting, and about how AI output is about validating the emotions of the listener rather than meaningful content.

Imagine you run 365 services, and each goes down 1 day a year.

If those are all on the same day, this would report you having 99.7% uptime.

If instead, each service goes down 1 day per year but on different days, this would report you having 0% uptime.

Despite the same actual downtime for any given service.

The truth is somewhere in the middle, that github has run degraded for a significant amount of time.

But I don't think it is fair to take an incident like this one[1], where 5% of requests were incorrectly denied authorisation, and count it the same as you would the whole of github being down.

[1] https://www.githubstatus.com/incidents/02z04m335tvv

I hadn't realised that it was now long defunct, with its last release in 2010.

https://en.wikipedia.org/wiki/XChat_(IRC_client)

It's a fantastic game, one of the all-time greats, and there are tricky parts to execute, but it's not particularly challenging in terms of puzzling.

A common "failure" of DRY is coupling together two things that only happened to bear similarity while they were both new, and then being unable to pick them apart properly later.