Yeah. I keep meaning to dig into Blazor but it seems overwhelming at first (especially because I'm mainly a C# dev due to Unity and a lot of the .NET jargon is foreign to me).
There seems to be more lightweight "c# to web-assembly" routes than might be worth investigating.
Just out of curiosity, what kind of a moderately-complex codebase can be migrated to a browser setting from one that C# is currently running on without considerable refactoring or adaptations ?
It generates and manipulates 3d geometries. I currently render it in Unity but it would be nice to have a lightweight WebGL native library that could be used by three.js, A-Frame etc.
There is: "This place is standardized on X" (what is way more common than it should be.)
And: "X-developers are cheaper" (and then, developers stay stuck there because it's a large market, but shouldn't.)
And there's the real reason why one should want to use the same language everywhere, that is to provide greater integration between frontend and backend on a framework (but then, currently it's mostly React that tries to do that and it doesn't get good results out of it - so much that developers refuse to use that feature).
In-browser programming is 5% about js as a language and 95% about DOM, html, various browser apis etc. - all the examples for the above are in js anyway so at the very least one needs to become proficient reading js to do anything useufl.
