The browser is kind of its own sandboxed environment in a way now granted the browser has been getting more and more features and abilities to access the file system. So it's these things just can't like willy-nilly access your file system so it gives you a little bit more of a sandboxed environment. It spins up a sort of like a pseudo Linux VM where they have basically just reimplemented a lot of the APIs. They are then running it in the browser and you can stream the output from it runs it in an iFrame I'll talk about that in just a second.
In this Hasty Treat, Scott and Wes talk about two new services that allow you to run Node in the browser, WebContainers + NodeBox. Why Node in the browser? How does it work? And what are the differences and limitations of the services?
Sentry - Sponsor
If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up.
Show Notes
Tweet us your tasty treats