Summary
Colin Eberhardt looks at some of the internals of WebAssembly, explores how it works ‘under the hood’, and looks at how to create a (simple) compiler that targets this runtime.
Bio
Colin Eberhardt is the Technology Director at Scott Logic, a UK-based software consultancy where they create complex application for their financial services clients. He is an avid technology enthusiast, spending his evenings contributing to open source projects, writing blog posts and learning as much as he can.
About the conference
Software is changing the world. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.
- SEPTEMBER 23, 2020 | 9AM EDT / 3PM CEST
Learn software architecture best practices. Discover practical strategies for Cloud Native, Managing Migrations and Leadership.
- September 22nd, 2020, 10:00AM PDT
How to pay down technical debt in JavaScript applications.
Transcript
Eberhardt: My name is Colin Eberhardt. I work for a UK-based software consultancy called Scott Logic. In time honored tradition, I’m going to start off by plugging my book. This is, “What Is WebAssembly” by O’Reilly. It arrived in the post just a few weeks back. It looks good from that direction, less good from that direction. I call it a book. It’s more of a pamphlet, really. There’s my pamphlet.
Why We Need WebAssembly
Why do we need WebAssembly? That can be summed up in this one slide alone. JavaScript these days is a compilation target. It wasn’t intended for this purpose. When it was first invented just over 25 years ago, it was intended as a way to add just a little bit of interactivity into what was otherwise quite a static web. However, 25 years from then, we’re using it in quite a different way.
#compilers #webassembly #web development #qcon london 2020 #transcripts #development #presentation
