I totally agree with you on one thing: WASM will become the "lingua franca" of integration for industries such as banking and e-commerce. A software engineer with 15 years of coding exp here.
Thanks for the video series. I think of WAT2WASM more as a "web assembler" translating "WAT" (WebAssembly textual source) to (WebAssembly Virtual Machine Language [ VML ] akin to P-Code) and high-level languages like Javascript (web "BASIC" or web "Pascal"). This is because WAT2WASM is more like Assembly to Machine Language translation versus compilers which are higher up in the totem from Low, to Intermediate, to High-level programming languages. Assembly language for various native CPUs were considered intermediate-level languages. A step closer to the "bare metal" of machine language than C or Pascal or BASIC were at source. BASIC, albeit were commonly interpreted, did have compilers that existed. On 8-bit computers like C64, we had many. Several that compiled to P-Code which was a VM bytecode thing much like this is. Not quite ML speed but considerably faster than interpreters and gave performance boosts. It is unclear how the speed is compared to JIT compiled JS once it had been ran through JIT compiling but this is a binary that is platform independent than native binary of x86 or ARM or whatever.
Just bear in mind that what I said about WAT text in relation to binary format is analogy not as exactly literal like assembly language to Machine language because a direct parallel of WASM to assembly like text would be to inverse the hex values of machine code to the instruction in the instruction set table in binary but really... close enough. You can if you are careful eye, can correlate the WAT textual instruction to the particular hexadecimal values and the particular instruction set and opcode of the WASM binary in a textual mneumonic style that would correlate in some fashion with the instruction set table for the WASM version (presuming a future version of WASM can break compatibility with the older/current if they want to make room for expanding and the version number begins to have greater importance in the future at some point in the future. However, WASM binary hex code values will or should correlate closely with the instruction set table of the particular WASM version. WASM version would matter, of course. Si it would be conceivable to write an almost pure WASM Assembly Opcode/Operand mneumonic format to hexadecimal format. When I say, mneumonic style, I am referring to ( webassembly.github.io/spec/core/appendix/index-instructions.html ) but of course, there is stuff one has to kind of observe between WAT to WASM and analyzing the hex values and understanding the structure of the system altogether. But at first, working in WAT then "assemble" to WASM would be a good place to start and over time, explore how to manipulate the wasm binary code and then write code straight in the binary for those that want to explore that but I would not say it would be practical for professional work involving a lot of code. Coding WAT by hand, maybe if you get it down to science, you can do some impressive stuff but in a lot of cases, most just won't get into that level of tight woven advanced handwritten webassembly like some ML coder did in the demo scenes or old school programmers of the age of NES/SNES/DOS/C64/Amiga era and how we got into the nuts and bolts.
Cool video. I'd been following WASM for a while, but thought "it can't access the DOM, javascript is already pretty fast - who cares?". This gave me some more stuff to ponder.
Hi Chris, I have recently discovered your channel, and is awesome I enjoy it. Your video makes me think a few questions: what medium WASM runs above, an engine as V8? Can it run apart from a browser? Thank you in advance
I am not sure if your example of Docker being bloaty is applicable in Linux. Since, Docker's underlying technology is Linux namespace, it makes sense that at the end of the day if you want to install it on any other non-Linux OS, you have to use a VM (e.g. Docker Desktop, WSL). I would argue that wasm is not going to replace linux container, not only from the level of control, but also the overhead introduced from the containerisation and inability to directly interface with non-wasm system libraries.
I've seen some services (beyond cloud providers) allowing users to upload code to handle specific workflows: Things like transactional mail and authentication services. Pretty much all of them would accept JS scripts and would expose a well defined API to interact with the service. Isn't JS already sandboxed enough for these scenarios?
@@chrishayuk there's also V8 isolates, which are also a popular choice for running Wasm. But I guess you were thinking more of Wasm-specific runtimes like Lucet.
@@ChumX100 yeah, i was.. but i like your call on V8 isolates.. i think cloudflare uses that for their edge network.. i think this could be some interesting vid ideas.. i like it.. THANK YOU!!!
![“อาร์ต พศุตม์” เกือบเอี่ยวทุกคดีดัง เอ๊ะไว้ก่อน ไม่มีอะไรได้มาง่ายๆ | แฉ 16 ต.ค. 67 [2/3] | GMM25](http://i.ytimg.com/vi/0Gx-0-kUBv8/mqdefault.jpg)
It gives Java's "write once run everywhere" capabilities to any compiled language.
I insta-subscribed to your channel based on the content and quality level of this video alone. Great job!
Yay, thank you!
I totally agree with you on one thing: WASM will become the "lingua franca" of integration for industries such as banking and e-commerce. A software engineer with 15 years of coding exp here.
Great video! Been trying to wrap my mind around the benefits of WASM. Thank you 🙏🏾
You have became an instant click TH-cam channel. What a great content you deliver, wow.
Wow, thanks! glad you're enjoying the content
Very nice explanation. Thank you very much.
Glad it was helpful!
Thanks for the video series. I think of WAT2WASM more as a "web assembler" translating "WAT" (WebAssembly textual source) to (WebAssembly Virtual Machine Language [ VML ] akin to P-Code) and high-level languages like Javascript (web "BASIC" or web "Pascal"). This is because WAT2WASM is more like Assembly to Machine Language translation versus compilers which are higher up in the totem from Low, to Intermediate, to High-level programming languages. Assembly language for various native CPUs were considered intermediate-level languages. A step closer to the "bare metal" of machine language than C or Pascal or BASIC were at source. BASIC, albeit were commonly interpreted, did have compilers that existed. On 8-bit computers like C64, we had many. Several that compiled to P-Code which was a VM bytecode thing much like this is. Not quite ML speed but considerably faster than interpreters and gave performance boosts. It is unclear how the speed is compared to JIT compiled JS once it had been ran through JIT compiling but this is a binary that is platform independent than native binary of x86 or ARM or whatever.
Just bear in mind that what I said about WAT text in relation to binary format is analogy not as exactly literal like assembly language to Machine language because a direct parallel of WASM to assembly like text would be to inverse the hex values of machine code to the instruction in the instruction set table in binary but really... close enough. You can if you are careful eye, can correlate the WAT textual instruction to the particular hexadecimal values and the particular instruction set and opcode of the WASM binary in a textual mneumonic style that would correlate in some fashion with the instruction set table for the WASM version (presuming a future version of WASM can break compatibility with the older/current if they want to make room for expanding and the version number begins to have greater importance in the future at some point in the future. However, WASM binary hex code values will or should correlate closely with the instruction set table of the particular WASM version. WASM version would matter, of course. Si it would be conceivable to write an almost pure WASM Assembly Opcode/Operand mneumonic format to hexadecimal format. When I say, mneumonic style, I am referring to ( webassembly.github.io/spec/core/appendix/index-instructions.html ) but of course, there is stuff one has to kind of observe between WAT to WASM and analyzing the hex values and understanding the structure of the system altogether. But at first, working in WAT then "assemble" to WASM would be a good place to start and over time, explore how to manipulate the wasm binary code and then write code straight in the binary for those that want to explore that but I would not say it would be practical for professional work involving a lot of code. Coding WAT by hand, maybe if you get it down to science, you can do some impressive stuff but in a lot of cases, most just won't get into that level of tight woven advanced handwritten webassembly like some ML coder did in the demo scenes or old school programmers of the age of NES/SNES/DOS/C64/Amiga era and how we got into the nuts and bolts.
after 12 seconds of starting the video I subscribed , keep up the good work .............
Glad you liked
Cool video. I'd been following WASM for a while, but thought "it can't access the DOM, javascript is already pretty fast - who cares?". This gave me some more stuff to ponder.
Hi Chris, I have recently discovered your channel, and is awesome I enjoy it. Your video makes me think a few questions: what medium WASM runs above, an engine as V8? Can it run apart from a browser? Thank you in advance
yes, it very much can independent of browser. check my webassembly playlist, loads more on WASM
I am not sure if your example of Docker being bloaty is applicable in Linux. Since, Docker's underlying technology is Linux namespace, it makes sense that at the end of the day if you want to install it on any other non-Linux OS, you have to use a VM (e.g. Docker Desktop, WSL). I would argue that wasm is not going to replace linux container, not only from the level of control, but also the overhead introduced from the containerisation and inability to directly interface with non-wasm system libraries.
Great Video! more contents like this please!
I've seen some services (beyond cloud providers) allowing users to upload code to handle specific workflows: Things like transactional mail and authentication services. Pretty much all of them would accept JS scripts and would expose a well defined API to interact with the service. Isn't JS already sandboxed enough for these scenarios?
they're usually ran within a container in the backend, so heavier weight
@@chrishayuk there's also V8 isolates, which are also a popular choice for running Wasm. But I guess you were thinking more of Wasm-specific runtimes like Lucet.
@@ChumX100 yeah, i was.. but i like your call on V8 isolates.. i think cloudflare uses that for their edge network.. i think this could be some interesting vid ideas.. i like it.. THANK YOU!!!
hope than business people will believe in the wasm possibilities )
The music is loud and the volume is chaotic in the intro
agree, hence why i cut it for later videos. a bad experiment, appreciate your feedback
@@chrishayuk I didn't realize it was old. It's good content in any case. I had been watching your other videos; keep up the great work!
Cheers, appreciate it, weirdly I think webassembly is gonna become very relevant for ai. I think the thoughts in this video hold pretty true
WHY THE MUSIC IS SO LOOOOOOUD???
Good content, crap audio and background distracting 'music?'.
still experimenting on the audio. i've adjusted latest video. glad you enjoy the content
@@chrishayuk I think the music is okay to give the exciting feeling about the content, but it should be quieter then I think it would be perfect.
@@chrishayuk Really nice content, btw. I found a painting web app that uses web assembly then it got me interested. Thanks.
you dont make any sense
I often don’t