4 ms·

Blazor is definitely not a shiny new technology. It's been around for years but still hasn't seen it's official release. Last significant bit of news from it w

Blazor is definitely not a shiny new technology. It's been around for years but still hasn't seen it's official release. Last significant bit of news from it was the "official preview" phase, back in April. If I understand it well, it WILL be released soon given that .NET Core 3 has just been released too.

dgellow 7y ago
April announcement here https://devblogs.microsoft.com/aspnet/blazor-now-in-official-preview/ https://devblogs.microsoft.com/aspnet/blazor-now-in-official.... > With this newest Blazor release we’re pleased to announce that Blazor is now in official preview! Blazor is no longer experimental and we are committing to ship it as a supported web UI framework including support for running client-side in the browser on WebAssembly.
perfectphase 7y ago
Blazor has been split into two versions, there is a server side and a client side version, both that share the same component model. The server side version went GA a last week with .Net core 3.0, the client side is looking like it will GA in April 2020. The reason given is that their not happy with the size of the payloads required for now, the aim to have everything compiled to webAssembly by then, not just the mono runtime that's running as an IL interpreter at the moment. The server side version is interesting, it ships DOM updates to the client from the server over a websocket (musch like OOUI https://github.com/praeclarum/Ooui https://github.com/praeclarum/Ooui). Not something that I'd use for production, but for quick internal projects which have the feel of a client side SPA, but while not requiring you to build the API layer it's quite neat.
- untog 7y ago
  > The server side version is interesting, it ships DOM updates to the client from the server over a websocket WebForms 2020! Amazing.
  - perfectphase 7y ago
    Yep, that's pretty much the aim :)
  - sebazzz 7y ago
    Except it is much more intuitive. A repeater- like construct (a foreach) just works. Collections just work. No thinking about data binding at the correct time in the life cycle of the page. You can even call front-end javascript in a sync-like (using async) matter. You can just call a javascript confirm if you like. It is awesome.
  - chusk3 7y ago
    I'd say more like Elm's Pheonix LiveView, to be honest.
- asdfman123 7y ago
  > The reason given is that their not happy with the size of the payloads required for now Question: how will they go about shrinking them? Will this happen in the near future? I've tried out Blazor before and the page doesn't load until you've downloaded everything. Will it always be that way, or will it be like JS eventually -- you see the page, and the JS loads in the background?

dgellow 7y ago

April announcement here https://devblogs.microsoft.com/aspnet/blazor-now-in-official-preview/ https://devblogs.microsoft.com/aspnet/blazor-now-in-official.... > With this newest Blazor release we’re pleased to announce that Blazor is now in official preview! Blazor is no longer experimental and we are committing to ship it as a supported web UI framework including support for running client-side in the browser on WebAssembly.

perfectphase 7y ago

Blazor has been split into two versions, there is a server side and a client side version, both that share the same component model. The server side version went GA a last week with .Net core 3.0, the client side is looking like it will GA in April 2020. The reason given is that their not happy with the size of the payloads required for now, the aim to have everything compiled to webAssembly by then, not just the mono runtime that's running as an IL interpreter at the moment. The server side version is interesting, it ships DOM updates to the client from the server over a websocket (musch like OOUI https://github.com/praeclarum/Ooui https://github.com/praeclarum/Ooui). Not something that I'd use for production, but for quick internal projects which have the feel of a client side SPA, but while not requiring you to build the API layer it's quite neat.

untog 7y ago
> The server side version is interesting, it ships DOM updates to the client from the server over a websocket WebForms 2020! Amazing.
- perfectphase 7y ago
  Yep, that's pretty much the aim :)
- sebazzz 7y ago
  Except it is much more intuitive. A repeater- like construct (a foreach) just works. Collections just work. No thinking about data binding at the correct time in the life cycle of the page. You can even call front-end javascript in a sync-like (using async) matter. You can just call a javascript confirm if you like. It is awesome.
- chusk3 7y ago
  I'd say more like Elm's Pheonix LiveView, to be honest.
asdfman123 7y ago
> The reason given is that their not happy with the size of the payloads required for now Question: how will they go about shrinking them? Will this happen in the near future? I've tried out Blazor before and the page doesn't load until you've downloaded everything. Will it always be that way, or will it be like JS eventually -- you see the page, and the JS loads in the background?