Recorded at Øredev 2018, Fredrik talks to Steve Klabnik about Rust and Webassembly. We talk a lot about error messages, based on Steve’s talk on how Rust handles and displays error messages. We discuss Rust’s error messages thinking an handling, but also error messages more in general, such how to think in order to produce error messages both developers and end users have a chance of understanding. Steve explains how and why the Rust compiler is switching from a pass-based compilation approach to a query-based approach to better facilitate partial recompilation upon smaller code changes. We also talk about Rust 2018, how Rust puts out new releases and what major features are on their way.
We then switch to talking about Webassembly. We discuss how Webassembly is moving along, among other things how it is getting better at playing well with others, enabling people to rely on Webassembly code without necessarily even needing to know about it.
Thank you Cloudnet for sponsoring our VPS!
Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at [email protected] if you want to write longer. We read everything we receive.
If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi.
Links
Steve KlabnikSteve was also in episode 245, talking about Rust, why the lucky stiff and a lot moreMozillaRustSteve’s presentation about error messages in RustSteve’s second presentation, about WebassemblyRust’s Github label for diagnostics/confusing error messagesICE - internal compiler errorAST - abstract syntax treeIR - intermediate representationLinkcheckerThe Rust bookRust by exampleAsync/await for RustWebassemblyEmscriptenWasmpack - bundles Webassembly code as a npm package - and puts it on npmSpectre and MeltdownThe host bindings proposalThe DOMWasm-bindgenPolyfillEthereum’s work with WebassemblySIMD - Single instruction multiple dataSIMD-support in Webassemblywebassembly.orgThe Webassembly specC and C++ through EmscriptenBlazor - C# to WebassemblyYes, there was a talk about Blazor by Steve SandersonSpidermonkey - Mozilla’s Javascript engineTitles
Something that should not be an afterthoughtHard actual workWhat messages to give or how to give themAny error message that’s confusing is a bugGit blame always returns your own nameThe internal deadline is tomorrowThe harder problemThe real test of being usableMore useful to more peopleBroader than just the DOMA host can do these thingsThe design is sort of not thereWe need more teachers and explainers