Hacker News new | ask | show | jobs
by krono 1418 days ago
FYI WebContainers are not a web standard, but this article sure does try its best to make it sound like one. Pretty off-putting and not at all necessary for such a great product as Stackblitz.

Firefox has added support for some webdriver APIs[1] that this proprietary "WebContainers" product depends on. That is all.

[1]: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...

2 comments

> Firefox has added support for some webdriver APIs[1] that this proprietary "WebContainers" product depends on

Hi, WebContainers does not depend on WebDriver BiDi. We did mention our interest in this new standard getting more momentum in other blog post (which might be the source of your statement?).

> We did mention our interest in this new standard getting more momentum

You keep calling it a standard.

The "working group" is some people on Discord. Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers.

> The "working group" is some people on Discord

Fair enough, we should correct our mention of WebDriver BiDi to "tentative standard". BTW, not sure if you hold some grudge against WebDriver BiDi in particular, we were merely saying "gee, I sure hope something better than WebDriver comes along, b/c E2E testing kinda sucks".

> Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers.

I am not sure what your objection is. We have a product, we're describing our efforts to port it to a new browser engine.

I guess I didn't understand what exactly you were talking about when talking about "this new standard": WebDriver BiDi or WebContainers.

WebDriver BiDi is on the standards track, that's true: https://w3c.github.io/webdriver-bidi/

I see, it seems we misread each other.
Just a regular day on HN
I think "this new standard" was referring to WebDriver BiDi, not WebContainers, so you might be misreading them.

That being said, I agree that the blog post made it sound like WebContainers is some kind of standard, and I also found that to be confusing.

Poor choice of words on my end, apologies.

The underlying technologies and the tooling that you've been building on top of it are great. I was merely pointing out the confusing or perhaps misleading writing style of this announcement.

no, there is more going on than that. MSFT is adding engineering to Ubuntu to embed private data and keys at boot time; Firefox and libssl are shipped as SNAPD containers; it is not possible to turn off remote updates in Ubuntu

see a pattern there?

> MSFT is adding engineering to Ubuntu to embed private data and keys at boot time

What? Where can I read about this?