One of the best performance tips is "do less" – transmit less data and do less processing. There are a million details but we will focus on transmitting less JavaScript. We are going to tackle it by doing more work at build time which means we start with almost zero JavaScript and only load more as the users interacts with the page. PUBLICATION PERMISSIONS:
Original video was published with the Creative Commons Attribution license (reuse allowed). Link: https://www.youtube.com/watch?v=V2yjXFPYjVA https://www.youtube.com/watch?v=1nNgaQA9gW8

Conditional rendering issues in JSX, forwardRef, dozens of ways to create refs, render props (yeah they still exist), act, non-extendable classes, SuspenseList (well, maybe in 10 years) and of course our good old friend useEffect. All these weird things are part of our favourite library (not a framework™) and yet we still use and love it. Why actually? Let's talk about. Disclaimer: This is not a very serious talk, mostly … PUBLICATION PERMISSIONS:
Original video was published with the Creative Commons Attribution license (reuse allowed). Link: https://www.youtube.com/watch?v=25QQcPSzH8Y https://www.youtube.com/watch?v=-NPUjrjusPA

In 2019, the WASI standardization effort was started in the WebAssembly CG as a way to bootstrap an ecosystem of safe, portable WebAssembly modules running outside (or inside) the browser. The starting point of the design, captured in WASI "Preview1", included tried-and-true POSIX concepts like files and directories. However, as the standards group worked to realize high-level goals including language neutrality, low-latency startup, low-overhead virtualization, heterogeneous host environments, fine-grained sandboxing and robust composition of programs from modules, the approach of mapping classic POSIX concepts into WebAssembly kept running into problems and a new approach had to be explored. Two years (and one pandemic) later, based on experience gained from Preview1, an improved design has emerged that splits the problem in two, factoring out a foundational "component model" layer that is implemented by the WebAssembly engine, providing a more lightweight, composable, declarative unit of code, along with new Wit and World syntax for defining WASI and other component interfaces. This talk will describe some of the original problems and how they are proposed to be addressed, present some examples of next-iteration WASI interfaces in action and discuss paths of incremental adoption. PUBLICATION PERMISSIONS:
Original video was published with the Creative Commons Attribution license (reuse allowed). Link: https://www.youtube.com/watch?v=phodPLY8zNE https://www.youtube.com/watch?v=DkpNqcfuPOM