AI-generated Key Takeaways
-
This episode discusses the Native File System API and its writeable file stream capabilities, along with coping mechanisms during lockdown.
-
Jake and Surma explore VR experiences, including Oculus Quest, Google Cardboard, and Beat Saber, and touch upon web-based VR content using three.js.
-
The discussion delves into technical web development topics like HTTP status codes for null search results, live vs static NodeLists, and Java bindings in the DOM spec.
-
They also cover off-main-thread processing with React, native module usage in production, issues with HTTP/2 push, and Rollup import hoisting.
-
The episode concludes with thoughts on workers, the actor model, Chrome Dev Summit, KaiOS and Mozilla's partnership, and content editable features.
In this episode we chat about:
- The Native File System API.
- Writeable file stream.
- Coping with lockdown.
- Jake and Surma geek out about the Oculus Quest.
- Google Cardboard.
- Google Daydream.
- Beat Saber.
- Jake's neighnbour caught him playing Beatsaber.
- Superhot VR.
- VR content in the browser.
- three.js + VR.
- Surma's blog post on WebXR.
- If a search returns 'no results', what should the status code be?
- Live
NodeLists. - Why do we have static
Nodelists rather than arrays? - Java bindings in the DOM spec.
- Off main thread + React.
- Using native modules in production.
- HTTP/2 push is problematic.
- Rollup import hoisting.
- Workers vs shared workers.
- Surma & Paul talk about the actor model.
- The Chrome Dev Summit website.
- KaiOS and Mozilla partner up.
- Content editable 'plaintext-only'.
designMode.- Jake IDB library.
- Jake takes TMI to an extreme.