> Also, don't forget that you can go open an issue or submit a PR to any of the major .NET repositories right now, and expect to have your work (assuming accepted) incorporated into an official .NET release within a year or so.

Yes! They also publish videos of their design review discussions - I submitted a cryptography-related PR a while back, and it was really cool to watch my proposal being discussed, and then even cooler when my code made it into dotnet :)

> And tooling, etc. Check out visual studio 2022

Don't forget JetBrains Rider - I switched from VS a few years ago, and haven't looked back. VS is great too, but in terms of performance and stability, Rider kicks it to the curb (IMO).

> Who needs timer ICs when you have a busywait while loop checking the high res timer...

A lot of people are concerned about power usage these days, particularly if these things are running off a solar cell.

And these days, most embedded controllers include some kind of timer anyway. Micropython has a timer interface that interrupts into a python subroutine. I use this for application level routines interfacing with a hardware watchdog.

Why couldn’t you do the same thing with C#? Being worried about power is fine and all, but I’d rather build the application and then analyze the actual performance and power draw to determine the appropriate solution for power efficiency. I’m sure there’s some WFI (wait for interrupt) available that could be used to solve this.

There's nothing wrong with C# -- as long as the tooling supports the processor you're targeting and the interrupt/sleep states of the micro.

If you're running off a battery say, then it's better to build your software from the start to optimize for the various sleep modes.

https://lastminuteengineers.com/esp32-sleep-modes-power-cons...