Comments by "xybersurfer" (@xybersurfer) on "Why WebAssembly Can't Win" video.

  1. being able to call the DOM directly from WASM certainly seems necessary, but i don't think that will magically solve the problem of having to first download huge runtimes. it seems unrelated
    3
  2. yep
    2
  3. agreed. also if the .NET team loaded some parts on the fly, then they probably wouldn't have to worry as much about tree shaking
    2
  4. getting tree shaking perfect seems like a waste of time because programs are inherently unpredictable. and to then turn say "WabAssembly Can't Win" because this on guy is making poor decisions, is silly. if tree shaking is so hard to get right statically, then it should be done more on the fly for things like reflection. people normally accept that there is a performance penalty for using reflection anyway. more statically typed languages like C# probably have an advantage here. i don't see the reason everything has to be put into 1 huge module that has to be downloaded. people need to take some lessons from how things are already work for JavaScript on the web (not just this guy). in JavaScript there are typically no modules, or you could say that the classes in the "modules" can be downloaded as separate files. it's similar for whole websites that are also not downloaded in full. from the outside, it looks like these people are trying to solve the wrong problems
    1
  5. that would be good, but it has nothing to do with the size of WASM modules that implementations force you to download
    1