Summary

In this chapter, we talked about different strategies we can use to debug and optimize our WebAssembly code. We discussed writing C macros, which allow us to easily remove calls to print to the console when we move from development into production. We talked about source maps, what they are, and how they can help us to debug our WebAssembly code from within a browser. We discussed using the debugger in both Chrome and Firefox to step through WebAssembly's source code. Finally, we discussed optimization in WebAssembly, what compiler options are available in Emscripten, and how we can go about improving our WebGL performance.