592 subscribers
Looks like the publisher may have taken this series offline or changed its URL. Please contact support if you believe it should be working, the feed URL is invalid, or you have any other concerns about it.
Go offline with the Player FM app!
Podcasts Worth a Listen
SPONSORED


1 Beyond Basketball: Championship Lessons for Success, with Tyler Summitt (Leadership, Sports, Personal Development, Business) 28:47
WebAssembly Future with Steve Klabnik
Archived series ("Inactive feed" status)
When? This feed was archived on January 29, 2023 11:24 (
Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 215101640 series 1435594
WebAssembly is a low-level compilation target for any programming language that can be interpreted into WebAssembly. Alternatively, WebAssembly is a way to run languages other than JavaScript in the browser. Or, yet another way of describing WebAssembly is a virtual machine for executing code in a low level, well-defined sandbox.
WebAssembly is reshaping what is possible to do in the web browser. A developer can write a program in Rust or C++, compile it down into a WebAssembly module, and call out to that module via JavaScript. This is very useful for running memory-sensitive workloads in the browser—such as 3-D games.
But WebAssembly is also useful for running modules outside of the browser. Why is that important? If you can already run C++ or Rust code outside of the browser by executing the program from the command line, why would you want to put the code into a WebAssembly module before executing it? One answer is security. WebAssembly modules have well-defined semantics for what memory they can access. WebAssembly could provide more reliable sandboxing for untrusted code.
Steve Klabnik is a software engineer at Mozilla, and he joins the show today to play the role of a WebAssembly futurist. We revisit the basics of WebAssembly and the current state of the technology. Steve talks Steve also describes the lessons of past web technologies such as Flash—and what they did right and wrong. We also explore the current and future applications of WebAssembly, which we will talk about in more detail in tomorrow’s episode.
The post WebAssembly Future with Steve Klabnik appeared first on Software Engineering Daily.
112 episodes
Archived series ("Inactive feed" status)
When?
This feed was archived on January 29, 2023 11:24 (
Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 215101640 series 1435594
WebAssembly is a low-level compilation target for any programming language that can be interpreted into WebAssembly. Alternatively, WebAssembly is a way to run languages other than JavaScript in the browser. Or, yet another way of describing WebAssembly is a virtual machine for executing code in a low level, well-defined sandbox.
WebAssembly is reshaping what is possible to do in the web browser. A developer can write a program in Rust or C++, compile it down into a WebAssembly module, and call out to that module via JavaScript. This is very useful for running memory-sensitive workloads in the browser—such as 3-D games.
But WebAssembly is also useful for running modules outside of the browser. Why is that important? If you can already run C++ or Rust code outside of the browser by executing the program from the command line, why would you want to put the code into a WebAssembly module before executing it? One answer is security. WebAssembly modules have well-defined semantics for what memory they can access. WebAssembly could provide more reliable sandboxing for untrusted code.
Steve Klabnik is a software engineer at Mozilla, and he joins the show today to play the role of a WebAssembly futurist. We revisit the basics of WebAssembly and the current state of the technology. Steve talks Steve also describes the lessons of past web technologies such as Flash—and what they did right and wrong. We also explore the current and future applications of WebAssembly, which we will talk about in more detail in tomorrow’s episode.
The post WebAssembly Future with Steve Klabnik appeared first on Software Engineering Daily.
112 episodes
All episodes
×



1 Global State Management with James Cowling 30:32


1 Browser Observability With Jay Khatri 43:40


1 JavaScript Supply Chain with Feross Aboukhadijeh 45:18


1 Micro-Frontends with Luca Mezzalira 46:35


1 Enterprise React Apps with Paige Niedringhaus 45:44


1 Learning React with Kent C. Dodds 51:13


1 React Final Form with Erik Rasmussen 39:01


1 Earthly and CLI Productivity with Adam Gordon Bell 44:23


1 Pragma: Video Games with Eden Chen 58:55


1 Flutter: Native Web and Mobile App Development with Allen Wyma 47:34


1 WorkOS: Making Enterprise-Ready Apps with Michael Grinich 46:02




1 Rust and Go Research with Linhai Song 49:53


1 React Best Practices with Kent Dodds (Repeat) 52:33
Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.