OCTO Speaker Series #6: Fred K. Schott

[idan]

Hello everyone! Welcome to the sixth installment of the OCTO Speaker Series, featuring Fred K. Schott! (twitter, github)

@idan will be hosting Q&A following the talk. We are using this discussions thread for questions — if you'd like our hosts to discuss a topic, add it to this thread! We'll keep this thread around and link the recording of the talk when it's ready.

Be kind and thoughtful — we take our code of conduct seriously.

[idan]

What about the distributed web, and technologies like IPFS, Beaker Browser, etc?

[idan]

loading public code via URL sounds scary, what’s the security story like?

[idan]

From @lucianoratamero:

How would I know at a project level what are the dependencies and their sizes? Something like Webpack Bundle Tracker.

[idan]

It's relatively clear that I want to WASM things that are perf sensitive. If I want to process images or data or other things that can happen "outside the main thread" — WASM offers me a lot of opportunities for performance.

• Where do you think the interaction point with regular code is going to be? A
• Are we eventually going to compiling stuff for the web like we compile other software — a compilation toolchain that targets WASM? What's that going to look like?

[keimlink]

How does this relate to web components?

[keimlink]

How are dependencies managed/pinned with Snowpack?

[msakrejda]

How do you think local-first functionality fits into these architectural changes? And how can we support user-centric local-first models while moving toward the UX benefits of the account-oriented (instead of machine-oriented) approach you discussed?

[jorgemmsilva]

[Soremwar]

There is already a cache system implemented in browsers. However, for the system to work the library must have the exact same origin so the browser knows it is indeed the same library, meaning you would lose those benefits if you hosted or bundled this dependencies yourself. So things like CDNs step in to solve that problem

[jorgemmsilva]

yes, I was thinking more than url caching.

some distributed system (like IPFS) where we could fetch a lib + incremental patches (not every website runs the same version of react for example), and the browser could leverage this for multiple websites. (like an internal node_modules)

mostly just a dumb idea :) but could be interesting for dependencies that are widely used.

[oscard0m]

Hello everyone! Welcome to the sixth installment of the OCTO Speaker Series, featuring Fred K. Schott! (twitter, [github]

Link is broken. This is the right one: sixth installment of the OCTO Speaker Series

[eaftan]

Hello everyone! Welcome to the sixth installment of the OCTO Speaker Series, featuring Fred K. Schott! (twitter, [github]

Link is broken. This is the right one: sixth installment of the OCTO Speaker Series

Fixed, thanks again!