44 ms·

You are comparing an open, non-proprietary compile target to a closed ecosystem. Admittedly, WASM is making slow progress (much to it due to Google actively/pa

You are comparing an open, non-proprietary compile target to a closed ecosystem. Admittedly, WASM is making slow progress (much to it due to Google actively/passively sabotaging it) but it is the closest we have got to a universal compile target. In particular, the combination with Rust could be a game changer and make whole categories of DSLs obsolete. It also has the potential to open FE work for people which categorically refuse to work with the mess that is the JS ecosystem.

giancarlostoro 3y ago
Got any examples of Google sabotaging WASM? First I have heard of this. I thought Apple was kind of since they seem to adopt some things somewhat slow or not at all.
- jamil7 3y ago
  WebKit has had a WASM implementation since 2017, the same as Chrome and Firefox as far as I know.
  - callahad 3y ago
    We all (Mozilla/Google/Microsoft/Apple) announced consensus for the WebAssembly MVP on February 28, 2017. Mozilla and Google shipped on-by-default in March, Apple in September, and Microsoft in October.
- brabel 3y ago
  Google is supporting WASM heavily, e.g. with their Android and Flutter teams both working hard on WASM support. They require Wasm GC, which the Chrome team has already implemented and Firefox is not far behind. https://docs.flutter.dev/platform-integration/web/wasm https://docs.flutter.dev/platform-integration/web/wasm https://chromestatus.com/feature/6062715726462976 https://chromestatus.com/feature/6062715726462976 https://www.youtube.com/watch?v=Nkjc9r0WDNo https://www.youtube.com/watch?v=Nkjc9r0WDNo
pid-1 3y ago
> Admittedly, WASM is making slow progress (much to it due to Google actively/passively sabotaging it) Since Google use Browsers as their app and as distribuition platform, I always thought that anything that made browsers easier to target vs native apps was a win for them.
pjmlp 3y ago
Hardly the best in anything.

giancarlostoro 3y ago

Got any examples of Google sabotaging WASM? First I have heard of this. I thought Apple was kind of since they seem to adopt some things somewhat slow or not at all.

jamil7 3y ago
WebKit has had a WASM implementation since 2017, the same as Chrome and Firefox as far as I know.
- callahad 3y ago
  We all (Mozilla/Google/Microsoft/Apple) announced consensus for the WebAssembly MVP on February 28, 2017. Mozilla and Google shipped on-by-default in March, Apple in September, and Microsoft in October.
brabel 3y ago
Google is supporting WASM heavily, e.g. with their Android and Flutter teams both working hard on WASM support. They require Wasm GC, which the Chrome team has already implemented and Firefox is not far behind. https://docs.flutter.dev/platform-integration/web/wasm https://docs.flutter.dev/platform-integration/web/wasm https://chromestatus.com/feature/6062715726462976 https://chromestatus.com/feature/6062715726462976 https://www.youtube.com/watch?v=Nkjc9r0WDNo https://www.youtube.com/watch?v=Nkjc9r0WDNo

pid-1 3y ago

> Admittedly, WASM is making slow progress (much to it due to Google actively/passively sabotaging it) Since Google use Browsers as their app and as distribuition platform, I always thought that anything that made browsers easier to target vs native apps was a win for them.

pjmlp 3y ago

Hardly the best in anything.