3 ms·

I can't say I see your point. What does switching to HTTP bring you? HTTP is just piping around ASCII. I don't think you're getting down voted for talking ab

I can't say I see your point. What does switching to HTTP bring you? HTTP is just piping around ASCII. I don't think you're getting down voted for talking about the downsides of UNIX. You haven't actually mentioned a downside of UNIX, you've just suggested that we should switch to some other model.

williamcotton 13y ago
Ok, so let's say you download a GitHub project... it has docs that run in a web browser, tests that run in python, some code that actually does something... it has some dotfiles for this and for that... well none of that DOES anything. It all depends on there being certain tools on your end of things... I'm saying that instead, we just ship all the tools along with the code... and you can do that in browserland, and that's NOT the UNIX-way at all! ...it has nothing to do with HTTP, it has to do with the web browser runtime as compared to the runtime built on top of a filesystem! UNIX land doesn't not play well when running any arbitrary stuff that comes it's way... sure, it might not have root, but, uhm, yeah if some code wipes out my entire user account, I'll be pretty bummed out... that's not gonna happen in the browser with it's sandboxed environment that has been battle-tested by trillions of page requests! Find me another runtime that is as many places and is readily available to run third-party, untrusted code, and I'll happily jump ship! (aint gonna happen!)