Can anyone translate this from marketing speak to developer speak? I’m genuinely not sure what this is. Is this like… WASM docker in the browser or what?
This looks really cool (I love anything with a filesystem API), but I'm unclear on the role of hosted proxies in this setup. Also, the licensing costs aren't clear.
"WebContainers rely on hosted proxies and server-side acceleration to enable truly instant development environments. By obtaining a WebContainer API license, your business can gain access to higher API rate limits, uptime reliability, and a range of benefits designed to help you maximize the potential of the WebContainer API in your organization."
Short of building my own using this API, does a self-hosted Codesandbox/Stackblitz alternative exist? I love the idea of spinning up web containers within my corporate network so I can prototype applications using internal APIs.
"Licensing is required for production usage of the API in a for-profit setting (feel free to prototype as much as you like without a license). If you're using the API to meet the needs of your customers, prospective customers, and/or employees you need a license to ensure continued access to the API as you scale."
Eric (StackBlitz CEO) here- you can actually self host StackBlitz! You’ll just need our Enterprise Edition (https://stackblitz.com/enterprise) which can be run on any cloud or on-prem. Happy to answer any questions you might have!
It's tempting to try to integrate this as an alternative to actual containers or fly.io but it seems to need to execute arbitrary npm installs on my server which defeats the purpose since the goal is to everything in the customer's browser instead of trusting their code on my server.
Er, I must be missing an important nuance here, can someone who understands this explain. What is the real world use case for this? I'm afraid I don't understand what this provides that either wasm or the browser sandbox does not.
https://learn.svelte.dev/tutorial/introducing-sveltekit was built with web containers. SvelteKit allows developers to create server-side APIs and do server-side rendering and web containers allow those server-side components to run in the browser.
Does "WebContainer API" mean "proprietary web service for accessing npm and git over http"?
Or is it "ECMAScript API of new open source WASM-based POSIX-style browser OS"?
The documentation doesn't seem to separate these two, and applying such name for the former would seem intentionally misleading to me, especially if it gets trademarked by commercial entity providing the service.
This is potentially exactly what I'm looking for to take Boot.dev to the next level. I'm a bit worried that it's too JS focused, but if I can hack in the other stuff I need with wasm then this gets really exciting. thanks for posting :)
FYI, in your homepage video explainer, the code contains the comment "Don't touch above this line", but I think you meant "below" given the purpose of the exercise.
It looks like they're loading in MDX (Markdown) for a lot of the pages
There are quite a few "static-site generator" templates that are easy to setup and customize and many of them are free to use! If I had to guess, I think they're using VitePress [1] here. Nextra [2] is also good for this kind of a website.
HN title is a little editorialized, making it sound like a new browser standard. Should be edited imo
The materials themselves also drip with exaggeration and hand-waving, talking about things like "the legacy cloud VM" (emphasis mine), "unmatched security", "spinning up the entire dev environment in milliseconds"
All of this is aside from the actual technology, which could be cool, I have no idea yet. But it rubbed me the wrong way
upghost|3 years ago
justanother|3 years ago
jaequery|3 years ago
pcj-github|3 years ago
"WebContainers rely on hosted proxies and server-side acceleration to enable truly instant development environments. By obtaining a WebContainer API license, your business can gain access to higher API rate limits, uptime reliability, and a range of benefits designed to help you maximize the potential of the WebContainer API in your organization."
brundolf|3 years ago
unknown|3 years ago
[deleted]
skeoh|3 years ago
vdfs|3 years ago
"Licensing is required for production usage of the API in a for-profit setting (feel free to prototype as much as you like without a license). If you're using the API to meet the needs of your customers, prospective customers, and/or employees you need a license to ensure continued access to the API as you scale."
ericmsimons|3 years ago
jacooper|3 years ago
nkko|3 years ago
koolala|3 years ago
unknown|3 years ago
[deleted]
ilaksh|3 years ago
drunkenmagician|3 years ago
benmccann|3 years ago
adamddev1|3 years ago
kasajian|3 years ago
But if you do, then this attempts to solve that problem.
If you're asking what's the use case for running nodejs in the browser? I say use your imagination.
avallach|3 years ago
The documentation doesn't seem to separate these two, and applying such name for the former would seem intentionally misleading to me, especially if it gets trademarked by commercial entity providing the service.
ericmsimons|3 years ago
This is closer to what the Bytecode Alliance is looking to do with WASI, which we're playing a small (but crucial) part in: https://blog.stackblitz.com/posts/bytecode-alliance/
> Does "WebContainer API" mean "proprietary web service for accessing npm and git over http"?
Kinda, we have plans to allow self hosting and more reg open source- more to come!
ashishbijlani|3 years ago
lanecwagner|3 years ago
supermatt|3 years ago
Spivak|3 years ago
kasperni|3 years ago
FinalDestiny|3 years ago
There are quite a few "static-site generator" templates that are easy to setup and customize and many of them are free to use! If I had to guess, I think they're using VitePress [1] here. Nextra [2] is also good for this kind of a website.
[1] https://vitepress.vuejs.org/
[2] https://nextra.site/
tnzk|3 years ago
wdb|3 years ago
brundolf|3 years ago
The materials themselves also drip with exaggeration and hand-waving, talking about things like "the legacy cloud VM" (emphasis mine), "unmatched security", "spinning up the entire dev environment in milliseconds"
All of this is aside from the actual technology, which could be cool, I have no idea yet. But it rubbed me the wrong way
scoopertrooper|3 years ago
https://github.com/stackblitz/webcontainer-core
unknown|3 years ago
[deleted]
bob778|3 years ago
helb|3 years ago
unknown|3 years ago
[deleted]