WebContainers: Run Node.js natively in the browser

Post by atatatat » Sun, May 23, 2021, 7:40 AM UTC

dmitriid wrote: post #207

atatatat wrote: post #193

Earlier quoted context omitted.

They're unable to keep anything close to security parity with Chromium — even with hundreds of millions of dollars. You're right — frankly, I don't look to Mozilla as the leader or voice of web development anymore.

> They're unable to keep anything close to security parity with Chromium Funny how you went from "Apple's chokehold on iPhone users" to "unable to keep anything close to security parity". I wonder in which respects Safari "can't keep up"? > I don't look to Mozilla as the leader or voice of web development anymore. - There are only two other independent browser engines of any importance, and their input is increasingl…

Post by atatatat » Sun, May 23, 2021, 7:42 AM UTC

ranguna wrote: post #204

atatatat wrote: post #197

Earlier quoted context omitted.

> Which stage is it? The stage where a majority of professional web devs (y'know, the people who aren't here!) still haven't even heard, or fully assimilated, the term "PWA" yet. > the "todo list" covers important issues around permissions, restricting file system access we etc. They've proven very capable of managing this in AOSP. > I think that Chrome plays fast and loose with web standards, and has essentially rep…

Can you give a few examples to backup your claim that chrome is head of Firefox in terms of security and privacy?

Post by dmitriid » Sun, May 23, 2021, 3:03 PM UTC

atatatat wrote: post #232

dmitriid wrote: post #205

Earlier quoted context omitted.

> compared to properly configured Chromium. Ah yes. Because that's exactly what you want from a browser: spend time properly configuring it to make it secure.

The configuration is for privacy. The security is inherent.

Post by dspillett » Mon, May 24, 2021, 1:58 PM UTC

giorgioz wrote: post #229

Galaco wrote: post #149

Earlier quoted context omitted.

> Faster than your local environment. Builds complete up to 20% faster and package installs complete >= 5x faster than yarn/npm. Above is a quote from the post. I feel like this is a stupid question, but how can running yarn/npm in a browser on my machine be faster than running yarn/npm on my machine? Particularly when each page load runs a fresh npm/yarn install? Nonetheless, this is a incredible piece of software t…

I've also asked myself this question. I think the comparison is not with a local environment but rather with running node/yarn/npm on a remote virtual machine/ci. This is my hypothesis, I have no proof that's what they meant.