tag:blogger.com,1999:blog-6393051114813114443.post7630575857328157021..comments2024-03-27T14:52:51.318-05:00Comments on Lee's Blog: Blazor WebAssembly vs Angular: Client Side ClashLee Richardsonhttp://www.blogger.com/profile/01314803491511307042noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6393051114813114443.post-34922260860423277402020-08-05T04:59:25.535-05:002020-08-05T04:59:25.535-05:00Very nice article. CongratsVery nice article. CongratsPepeuhttps://www.blogger.com/profile/14223044046280319880noreply@blogger.comtag:blogger.com,1999:blog-6393051114813114443.post-16686783312406538942020-07-28T01:46:53.406-05:002020-07-28T01:46:53.406-05:00Sure, that's what its for!Sure, that's what its for!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6393051114813114443.post-24713454083748830932020-07-27T10:17:03.169-05:002020-07-27T10:17:03.169-05:00Great comments, thank you! I'll incorporate t...Great comments, thank you! I'll incorporate these into the article if that's ok.Lee Richardsonhttps://www.blogger.com/profile/01314803491511307042noreply@blogger.comtag:blogger.com,1999:blog-6393051114813114443.post-33195416325578115672020-07-27T04:09:20.772-05:002020-07-27T04:09:20.772-05:00Great article!
Few comments:
1. CSS isolation is ...Great article!<br /><br />Few comments:<br />1. CSS isolation is coming in Preview 8 in a few weeks.<br />2. Debugger is shaky at best ATM, they did a lot of fixes after 3.2.0 in the Mono repo. Exception support has also been added recently. Let's hope that<br />3. I use Rick Strahls LiveReload tool. The MS folks are looking at that one to integrate a simple version in dotnet watch tooling.<br />4. There is a new experimental Razor editor that will solve many editor problems:<br />https://devblogs.microsoft.com/aspnet/new-experimental-razor-editor-for-visual-studio/<br />That should in the near future also include real-time template parsing so "Find usages" and "Go to definition" should work.<br />5. Not covered in your post, but performance is still a serious issue TBH. Mono.wasm runs in interpreted mode a factor 100x slower than AOT. They are working on improving the performance (.NET Core assemblies, interpret mode etc), but until threading & AOT is included (target 6.0.0) and WebAssembly DOM access (W3C spec is just finished), for complex scenarios you might need to dropdown to HTML again. <br /><br />It is still early days but the biggest pain points for building stuff are points 1-4, 5 you can work around depending on your use case.<br /><br />Anonymousnoreply@blogger.com