React native runs in the native ecosystem through a js-native-bridge and calls platform specifics system calls.
https://reactnative.dev/architecture/xplat-implementation
react is the <Components /> stuff in js
react-dom is the juice
Good find, when I read it I called bullshit but I got lost trying to understand the diagrams.
Another gotcha is the semantic decoder, they are just looping the model on itself "A cozy teddy bear" + fMRI random input => A teddy bear!!!
How would the statically typed WASM open an even wider hole? Assuming you mean that the size of wasm's hole is larger than js, not that their combined holes are larger than either one.
Wasm has more control over time and memory access than JS does. From a capabilities model, it is more secure, but from a threat model due to side channels, Wasm is a more effective tool than JS.
I am also an avid self learner but a good teacher / course it's inestimable.
Just watch a course like linear algebra from MIT with Gilbert strand and compare it to studying it alone. The difference is enormous .
Nice video but (unrelated to the IDE) in order to use a printf from js it was necessary to:
provide a js emulated syscall to c file
that calls another c function that calls back to js again
Yeah, it’s super weird when most people are expecting this to compile into JavaScript running in a browser. Nevertheless, to be fair, this isn’t a C, C++, or Rust to JavaScript compiler-compiler it’s a C, C++, or Rust compiler that targets WebAssembly. I realize this might read as overly pedantic but it explains why it makes sense to the implement the C interface. It’s also a reasonable optimization pass for a mature compiler when it knows that you’re targeting WebAssembly running in a browser.