The issue is that it's not a hobby, but a delivery. For delivery, you have to check commercial compatibility and long-term maintainability, so I'm not sure. Actually, I don't particularly like the XAML model itself, but the problem is the LTS policy and long-term viability. In delivery, technology choice is important. Because what can be maintained later is what matters. I have learned TypeScript, but I don't think you're wrong. It's sufficiently understandable for personal development and hobbies, but from a delivery perspective, it could be considered a risky choice.

I often build ERPs too, and for delivery I usually use TypeScript with Electron. C#'s biggest problem is mobile support. It's very strong on the game side, but weak on most phones. TypeScript, on the other hand, uses a bit more memory but is easier to wrap for mobile. You can just use Capacitor alongside Electron.

In my case, it's not a huge project—it's usually a small ERP dedicated to a local company in the region, so even if there are many employees, it's often only 100–200 people. At that scale, TypeScript holds up well enough. (For factory MES, there are tens of thousands of data points, but in that case it's usually fixed to C#.)

In this context, the mobile option in the ERP is good for charging customers, and it offers good extensibility as a reference option.

Unless WASM performance improves, there's still a bit of latency. On top of that, in my country there are few maintenance personnel.