For the love of DOM, why replace one dynamic language that is at least optimized for by the browser by another foreign one with an intermediate layer in between ?
I'm hitting that at the moment with a moderately complex c# codebase that would be really useful to run natively in the browser.
Yeah - I could rewrite it but I'd much rather not.
[0] -- https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor
There seems to be more lightweight "c# to web-assembly" routes than might be worth investigating.
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.
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).
>> Brython is designed to replace Javascript as the scripting language for the Web.