Avonelle's Blog

The cost of speed

By Avonelle Lovhaug on 9/30/2022

David Ramel at Visual Studio Magazine recently asked “Did .NET MAUI Ship Too Soon? Devs Sound Off on ‘Massive Mistake’”

I personally don’t have any experience with MAUI, so I don’t know the answer to this question. BUT I think this is yet another example of what happens when projects move too fast, over-promise and under-deliver.

There is definitely a segment of the developer population that can afford to jump early onto the ship of a new technology. But it is a considerably smaller segment than people think. Most of us have real problems we need to solve NOW. Pushing a new technology or approach before it is ready just costs us lots of time and money, and that is time and money we don’t have.

These days, we are supposed to embrace the high cadence of frameworks and APIs, but honestly, I much prefer the stability of the old .NET Framework days. I don’t need changes every few months. It isn’t that I don’t like new features – I do – but unstable frameworks and environments are a huge black hole that saps productivity. I don’t have the time for that. And frankly, I suspect most other developers don’t have the time for it as well.