3 ms·

Never underestimate the power of "But I already know lang X"

andybak 6y ago
As well as "I already have code in lang X" 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.
- wdroz 6y ago
  Maybe Blazor[0] could be a good fit for you. [0] -- https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor
  - andybak 6y ago
    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.
    - andybak 6y ago
      I think the complexity in Blazor might be a documentation issue. Every tutorial and quick start I can find assume you're knee deep in the ecosystem.
- seemslegit 6y ago
  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 ?
  - andybak 6y ago
    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.
seemslegit 6y ago
https://xkcd.com/801/ https://xkcd.com/801/ 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.
marcosdumay 6y ago
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).
- seemslegit 6y ago
  I'm having trouble imagining a place that writes browser code where X is not js in the first place.

As well as "I already have code in lang X" 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.

wdroz 6y ago
Maybe Blazor[0] could be a good fit for you. [0] -- https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor
- andybak 6y ago
  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.
  - andybak 6y ago
    I think the complexity in Blazor might be a documentation issue. Every tutorial and quick start I can find assume you're knee deep in the ecosystem.
seemslegit 6y ago
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 ?
- andybak 6y ago
  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.

seemslegit 6y ago

https://xkcd.com/801/ https://xkcd.com/801/ 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.

marcosdumay 6y ago

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).

seemslegit 6y ago
I'm having trouble imagining a place that writes browser code where X is not js in the first place.