5 ms·
Yes, sure. In my opinion, these are the main features: 1. You can have all the benefits of a static-strongly typed language such as C#. Which implies: better t
by jcmontx 7y ago
Yes, sure. In my opinion, these are the main features:
1. You can have all the benefits of a static-strongly typed language such as C#. Which implies: better tooling, less prompt to type errors, and more suitable for enterprise software.
2. You get the full power of .NET in the browser
And, if you are already using ASP.NET for your backend:
3. You can reuse a lot of code. This means almost no class duplication (like when you work with TypeScript).
Extra:
4. Blazor is pretty similar to Angular +2, so the learning curve is smooth if you either have experience with Angular or C#.
- shrewduser 7y agoWill we ever have an alternative UI framework that eschews html and CSS, perhaps rendering to webgl or something?
- dccoolgai 7y agoTry SVG
- okareaman 7y agoThe Flutter project at Google https://github.com/flutter/flutter https://github.com/flutter/flutter
- rpeden 7y agoWe already sort of do. Qt officially supports wasm and renders to a canvas element: https://wiki.qt.io/Qt_for_WebAssembly https://wiki.qt.io/Qt_for_WebAssembly And if you wanted to build your own wasm + canvas GUI toolkit, CanvasKit might be a good place to start: https://skia.org/user/modules/canvaskit https://skia.org/user/modules/canvaskit
- cm2187 7y ago* when we get client side blazor. Server side is a whole different thing.