> Faster than your local environment. Builds complete up to 20% faster and package installs complete >= 5x faster than yarn/npm. How? Isn't this using npm?
r/murderedbywords
WebContainers: Run Node.js natively in the browser
201–210 of 238 posts
Re: WebContainers: Run Node.js natively in the browser
#202I used to teach web development and was always frustrated with just how much effort went into setting up a machine. It would be really nice if a developer could just include a script tag in their project that setup a TypeScript compiler inside service worker. I managed to get the basics down, even fixing relative import statements. Requests like localhost:3000/main.tsx would compile and cache on the fly. There were a…
VS Code seems to allow this with Dev Containers. I can download a repo with a `.devcontainer.json` and be up and running in virtually no time, in a container.
Just wait till you try vscode devcontainers with GitHubs new code spaces.
Re: WebContainers: Run Node.js natively in the browser
#203This makes me want to quit webdev and never look back. Why the fuck are we recreating operating systems in the browser? We already have operating systems. We already have containers. We already have native code execution.
For fun?
Dude you live on such a black and white world
Re: WebContainers: Run Node.js natively in the browser
#204Earlier quoted context omitted.
> These are mostly a to-do list...which makes sense at this stage Which stage is it? Chrome is already shipping this, enabled by default. And the "todo list" covers important issues around permissions, restricting file system access we etc. > Do you think that Apple or Mozilla can stop webapps from taking their rightful place? I think that Chrome plays fast and loose with web standards, and has essentially replaced w…
> 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?
Re: WebContainers: Run Node.js natively in the browser
#205Earlier quoted context omitted.
> These are mostly a to-do list...which makes sense at this stage Which stage is it? Chrome is already shipping this, enabled by default. And the "todo list" covers important issues around permissions, restricting file system access we etc. > Do you think that Apple or Mozilla can stop webapps from taking their rightful place? I think that Chrome plays fast and loose with web standards, and has essentially replaced w…
> 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…
> 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.
Re: WebContainers: Run Node.js natively in the browser
#206This makes me want to quit webdev and never look back. Why the fuck are we recreating operating systems in the browser? We already have operating systems. We already have containers. We already have native code execution.
Because operating systems don‘t support seamless and secure distribution of cross platform software. Web browsers are currently the only secure sandbox we have.
Re: WebContainers: Run Node.js natively in the browser
#207Earlier quoted context omitted.
> It's not just about privacy of web APIs...it's about Apple's chokehold on iPhone users. Funny how you fully ignore Firefox's position
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 increasingly ignored by Chrome
- Who cares, go Chrome
This is not as good a take as you think it is.
Re: WebContainers: Run Node.js natively in the browser
#208Earlier quoted context omitted.
> These are mostly a to-do list...which makes sense at this stage Which stage is it? Chrome is already shipping this, enabled by default. And the "todo list" covers important issues around permissions, restricting file system access we etc. > Do you think that Apple or Mozilla can stop webapps from taking their rightful place? I think that Chrome plays fast and loose with web standards, and has essentially replaced w…
> 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…
> If the concerns are always "We can't keep up"
Safari and Mozilla: here are the security concerns, here are privacy concerns, here are concerns that the "specs" reflect internal APIs and are not actual specs.
HN: nah, concerns are always "we can't keep up"
No, those are not "we can't keep up".
Re: WebContainers: Run Node.js natively in the browser
#209I assume you still can't use UDP or bind to TCP sockets that are accessible outside of the browser?
TCP socket to Websocket :-
https://stackoverflow.com/questions/14928222/tcp-socket-to-w...
Re: WebContainers: Run Node.js natively in the browser
#210This makes me want to quit webdev and never look back. Why the fuck are we recreating operating systems in the browser? We already have operating systems. We already have containers. We already have native code execution.
Lol it seems that these days, any new significant web technology makes people want to ragequit their job for some reason https://news.ycombinator.com/item?id=26960946