Rick

I caught some of this. MonoGame is pretty compelling. As a lifelong C# dev who wants to make simple games with my kids, the more I can use C#, the better. I'll take the higher-level API trade offs, for now.

I'm a man of the people, that's why I use windows, to experience the peasant life.

@tsoding My typing speed went up significantly when I stopped doing that.

You don't write code by hands because you use AI. I don't write code by hands because I type with my dick. We are not the same.

@Aaronontheweb Fallback and trying to support every use case it’s ever written. Yes, Claude… you are allowed to make breaking changes to the code you JUST wrote. 😂

One of the most insidious tics LLMs have when coding is this obsession with adding "fallback" behaviors everywhere These are extremely toxic because they hide real bugs and most importantly, introduce lots of potential privilege escalation vulnerabilities everywhere

@robertmclaws @davidfowl At least we still have the tools to fix it ourselves. ConfigProvider.LoadAsync would be nice tho.

@davidfowl @rick01 There’s still time to fix it. Just like there’s still time to make ConfigurationProviders async.

Confession time: I cannot stand IOptions. The others, I can see... but IOptions solves nothing for me. If you're solving a problem with IOptions it's probably worth solving properly and not using framework 'magic'. I can't be alone on this.

@wdolek You can certainly make it fit. I just think there are better fits. I don’t typically use single config files, and the validation could be useful if you want validation by attribute. Not my style.

@rick01 I'm old enough to remember implementing things over configuration sections and 💩, and I find options better (namely - you don't need to reinvent wheel all the time)

@alexyakunin @davidfowl I would stop way short of calling it the worst. .NET has plenty of baggage, but we make it worse by abusing patterns and forgetting that .NET also lets us create whatever we want.

@davidfowl @rick01 Sorry, but that's one of the worst inventions in .NET. Especially in k8s age, when your services restart smoothly on way more significant changes than just a configuration related one.

@davidfowl Agree. We certainly love our ceremony. This is aimed at the folks who overcomplicate it. I really dig the direction you all, and dotnet have been headed. 👌🏻

@rick01 I had a hand in creating this. IOptionsMonitor and IOptions<T> should have been the same thing. People over complicate it, it’s just a factory.

@ExtinguishedEng Really? It’s usually the purists that refuse to deviate from IMicrosoft. I see it online and in Enterprise™️ code all the time.

@rick01 I've never used it or seen it used.

There's an ever so slight use-case that I'd concede for library authors that want to opt-in for the validation. Even if I wouldn't use it.

@inforhino @rick01 There is a validation pipeline you can use for ioptions. But it's a very lightweight abstraction over configuration and it's also fine to directly read configuration. Configuration handles multiple sources and refreshing.

@dariogriffo Dario gets it.

Is part the INonsense in dotnet. Solves nothing but allows to mock some sh#t that does not need to be mocked. That validation on startup is as useful as a review mirror on a plane. We use sealed records, register them via convention (all them end with Settings, so we register the section by name - Settings) and that's it. If your app fails at start you have failing processes that you need to fix, not add some crap.

@andyboothuk IOptions doesn't fit anywhere for me. I'd rather just use a POCO and register it with DI.

@rick01 IOptions doesn’t fit config for immutable environment deployments?

I'm trying to build an agent that has access to all my credentials, all the time. I'll give it my 1password account. I want it to do everything.

x.com/timeimmemorial… "Honey, I'm headed to Home Depot." *Me, on the way to Home Depot.*

Chuck Norris didn’t write dotnet, but he did use it every time he used a government website.

@rick01 Oh no. There's a motivational speaker.

Oh no. It's company annual meeting day. Why do companies act like this is supposed to be some kind of profound thing, when it's really just a bunch of stuff that could be in an email that I could have AI summarize?

I'll always remember Chuck Norris as the man who changed the course of dodgeball history by casting the deciding vote that allowed Average Joes to play in the championship of the Las Vegas International Dodgeball Open where they upset the heavily favored Globo Gym Purple Cobras. RIP. 🙏