- Learn WebAssembly
- Mike Rourke
- 269字
- 2021-08-13 15:38:52
Role in the development process
The text format allows for the representation of a binary Wasm module in textual form. This has some profound implications with regard to the ease of development and debugging. Having a textual representation of a WebAssembly module allows developers to view the source of a loaded module in a browser, which eliminates the black-box issues that inhibited the adoption of NaCl. It also allows for tooling to be built around troubleshooting modules. The official website describes the use cases that drove the design of the text format:
? Presentation in browser development tools when source maps aren't present (which is necessarily the case with the Minimum Viable Product (MVP)).
? Writing WebAssembly code directly for reasons including pedagogical, experimental, debugging, optimization, and testing of the spec itself.
The last item in the list reflects that the text format isn't intended to be written by hand in the course of normal development, but rather generated from a tool like Emscripten. You probably won't see or manipulate any .wat files when you're generating modules, but you may be viewing them in a debugging context.
Not only is the text format valuable with regards to debugging, but having this intermediate format reduces the amount of reliance on a single tool for compilation. Several different tools currently exist to consume and emit this s-expression syntax, some of which are used by Emscripten to compile your code down to a .wasm file.
- Java范例大全
- Spring 5企業級開發實戰
- Python從小白到大牛
- Java應用開發與實踐
- C語言實驗指導及習題解析
- Hands-On Automation Testing with Java for Beginners
- Mastering JavaScript High Performance
- Web前端應用開發技術
- R語言數據可視化:科技圖表繪制
- Buildbox 2.x Game Development
- RocketMQ實戰與原理解析
- Visual Basic程序設計全程指南
- UX Design for Mobile
- Software-Defined Networking with OpenFlow(Second Edition)
- 基于JavaScript的WebGIS開發