5 ms·

.NET team is also looking seriously in some C# love for WebAssembly eco-system. Its not a real project here yet but we have made some progress, check out this g

.NET team is also looking seriously in some C# love for WebAssembly eco-system. Its not a real project here yet but we have made some progress, check out this great interview: .NET Rocks! #1455 - WebAssembly and Blazor with Steve Sanderson https://www.youtube.com/watch?v=cCdF9-q4n5k https://www.youtube.com/watch?v=cCdF9-q4n5k

jamesXswift 9y ago
Awesome!
yodon 9y ago
I'm sure some here will laugh but I cannot wait for the day I'm able to ditch JavaScript and TypeScript and just write all my in-browser code in C# via WebAsm.
- londons_explore 9y ago
  Downloading .NET Framework v4.0 WASM Edition... 1%... 4 GB to go.
  - yodon 9y ago
    The download for the fully functional app in the video is ~300K, of which ~100K is bootstrap.js, so no this is not a lot of webasm being talked about to provide .NET support
    - tym0 9y ago
      From the github (https://github.com/SteveSanderson/Blazor https://github.com/SteveSanderson/Blazor): > Is this actually .NET in the browser? > It's not the regular .NET Framework or .NET Core runtime. It's a third-party .NET runtime called DotNetAnywhere, which has been updated and extended in various ways to support being compiled to WebAssembly, to load and run .NET Core assemblies, and with some additional functionality such as basic reflection and so on. > Can I build a real production app with this? > No. It's incredibly incomplete. For example, many of the .NET APIs you would expect to be able to use are not implemented.
- pedrocr 9y ago
  I think this is true of any language that isn't Javascript or one of its derivatives. When writing web apps we've had this strange setup where the server side can be any language but the browser side had to be JavaScript. It makes it hard to write your code only once and then use it in both contexts which is useful for things like input validation where you want to run it client side to give good and fast feedback in forms but need to do the same validation server side anyway. It also limits programmers to using JavaScript whether they like it or not. This has led to solutions like Google's GWT and on the reverse direction to the popularity of JavaScript on the server side. Hopefully that limitation is finally lifted and the choice of languages for the web becomes much less constrained. Discussions about the flaws of JavaScript are also often very animated because people that don't like it feel forced to use it to be able to program for the web. Hopefully this fixes that too.
- flavio81 9y ago
  +1000 Me too! C# or Common Lisp or Python or whatever, choosing the best choice for the specific project and circumstances.

jamesXswift 9y ago

Awesome!

yodon 9y ago

I'm sure some here will laugh but I cannot wait for the day I'm able to ditch JavaScript and TypeScript and just write all my in-browser code in C# via WebAsm.

londons_explore 9y ago
Downloading .NET Framework v4.0 WASM Edition... 1%... 4 GB to go.
- yodon 9y ago
  The download for the fully functional app in the video is ~300K, of which ~100K is bootstrap.js, so no this is not a lot of webasm being talked about to provide .NET support
  - tym0 9y ago
    From the github (https://github.com/SteveSanderson/Blazor https://github.com/SteveSanderson/Blazor): > Is this actually .NET in the browser? > It's not the regular .NET Framework or .NET Core runtime. It's a third-party .NET runtime called DotNetAnywhere, which has been updated and extended in various ways to support being compiled to WebAssembly, to load and run .NET Core assemblies, and with some additional functionality such as basic reflection and so on. > Can I build a real production app with this? > No. It's incredibly incomplete. For example, many of the .NET APIs you would expect to be able to use are not implemented.
pedrocr 9y ago
I think this is true of any language that isn't Javascript or one of its derivatives. When writing web apps we've had this strange setup where the server side can be any language but the browser side had to be JavaScript. It makes it hard to write your code only once and then use it in both contexts which is useful for things like input validation where you want to run it client side to give good and fast feedback in forms but need to do the same validation server side anyway. It also limits programmers to using JavaScript whether they like it or not. This has led to solutions like Google's GWT and on the reverse direction to the popularity of JavaScript on the server side. Hopefully that limitation is finally lifted and the choice of languages for the web becomes much less constrained. Discussions about the flaws of JavaScript are also often very animated because people that don't like it feel forced to use it to be able to program for the web. Hopefully this fixes that too.
flavio81 9y ago
+1000 Me too! C# or Common Lisp or Python or whatever, choosing the best choice for the specific project and circumstances.