This Task code, for example doesn't work.
Enum.map(0..10, fn(_) ->
Task.async(fn -> IO.puts("new process") end)
end) |> Task.await_many()
The blackbox can of course return the state of UI to be rendered/pathced, but that doesnt unlock much (if any) interesting capabilities for amount of overhead it adds
The blazor adoption probably isn't even that bad, but it's hard for MS to shake this stigma since so many people got burned on Silverlight and don't ever want to make the same mistake.
- Technical issue with blazor performance or blazor makes perf regressions hard to fix
- blazor technical framework encourages programming style that is bad for perf
- blazor or blazor ecosystem attracts programmers that can't deal with perf issues
https://github.com/software-mansion/popcorn
Couldn’t find any link to it on the article
nelsonic•4h ago