WebAssembly is (hopefully) the death of Javascript. They're a standard (not Microsoft) way of creating standard code blocks for browsers.
Blazor is just Microsoft's implementation of creating Web Assemblies with C#, but you will be able to use any language you're comfortable with. If you like your C#, you can keep your C#.
In summary: Web Assemblies: Good! Blazor: Up to you.
Eric
On Tue, Jan 21, 2020 at 8:43 AM Charlie Coleman ccbibleman@gmail.com wrote:
I have learned my lesson. I am never using a Microsoft-based technology ever again (if at all possible).
Build Web Apps with C#? No thanks. I was building "web apps" with VFP just fine thank you (don't bother with the diatribes about 'running in a browser' crap - that really has nothing to do with the power of the internet). So now I'm building them just fine with PHP, Javascript, (Python is on he horizon as well) with nary a worry about licensing, and with as much control over low-level 'under the hood' stuff as I want, etc. The open source world has its problems, but I'm never going back (don't bother with the diatribes about MS being all about open-source now... again, I've learned my lesson with that company).
-Charlie
On Tue, Jan 21, 2020 at 4:35 AM Alan Bourke alanpbourke@fastmail.fm wrote:
I've been intermittently having a look at it since it started as an experimental project.
Is it better than using JavaScript? Anything is better than using JavaScript IMO.
As is ever the case with Microsoft there are variants of it -
client-side,
server-side and now one integrated with Electron for building desktop
apps.
In many use cases I would definitely say it's a nail in the JavaScript coffin.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]