The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
It looks really interesting, and I want to use it, but it's experimental status keeps me from doing so.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I think I replied to something similar a bit back, but for the record...
Blazor's big advantage is that you get to use the same language on client and server and it's a real language, not a toy language. Those two things in and of themselves should make everything else obsolete for the most part, IMO. And of course they are getting ever closer to a practical WASM based client, which makes it even more appealing.
It's pretty easy to use and to create new components. It is HTML/CSS based ultimately, which sucks, but that is an equally distinct suckage quotient for pretty much all its competitors so it's a wash in terms of comparisons.
It's pretty straightforward to dynamically generate content, though it has limitations in terms of component inheritance wrt to component containment, which kind of sucks and they apparently don't care enough about that to do anything about it since they silently closed my issue last week on the matter.
It has a quite flexible embedded code/data in HTML scheme that makes it pretty easy to just embed references to component members and have them become part of the HTML, or to easily generate HTML content in place with code snippets. And/or you can have 'code behind' for much more complex processing.
However, because it's HTML based but it's sort of 'double buffered' in that they maintain their own hierarchy and go from that to HTML, changes can't really automatically show up. You have to force a refresh in lots of cases to get that to happen, and it's easy to miss places where you need to do that.
Ghoti is an artificial word used to illustrate irregularities in English spelling. It is a respelling of the word fish: i.e., it is supposed to be pronounced /ˈfɪʃ/. It is made of these phonemes: gh, pronounced /f/ as in tough /tʌf/;