5 ms·
Sometimes a program running in the browser will be valuable when it's full window. Would I complain if I could run a full version of Word or Excel in the brows
by j45 8y ago
Sometimes a program running in the browser will be valuable when it's full window.
Would I complain if I could run a full version of Word or Excel in the browser? The browser would become a universal interface in another way and decrease our reliance on particular operating systems.
- black_puppydog 8y agoYeah, or a full version of a monero miner...
- cmiles74 8y agoIn my experience, the application-on-browser products consume far more CPU and RAM than the application-on-OS products. For me, that's a pretty big deal: I need the laptop to run as long as possible on a charge. Right now, I would complain if I _had_ to run a full version of Word or Excel in the browser. Perhaps Web Assembly will drive this power usage down. But as it stands now, I actively avoid more than one of these app-on-browser products at a time.
- baybal2 8y agoWell, modern JS is MORE performant that classical scripting languages in benchmark cases, but the fact is that your browser freezes on half of js CRUDs that do data processing, while an analogous Perl application works at near light speed in comparison. In half cases like that, stuff like sorting, list comparison, deduplication are done in a way that will score low mark even by standards of first year university program. This is telling of web development industry's approach to doing business. The most horrid examples of "LAMP sweatshops" of 10 years ago pale in comparison to what the industry has devolved into these days. My own experience being an involuntary webdev for 3 years left me with following impressions: 1. Webdev is the largest commercial development niche in the whole tech industry. Everything else pales in comparison. It is also about making money quickly. A webapp or even a promo page SPA for a major consumer brand these days can cost up to $100k easily. $100k does not seem a lot to most people here, but such money can be well offered for a 1 month project for a team of of 6-8 professionals. 2. The industry is dominated by shops with 20 to 30 people headcount. Web dev studios generally don't scale much above that because of talent flight. Loss of a single senior dev who supervises hordes of lowest tier mule coders is often the end of a business for most of companies. 3. People from "big dotcom" world are near oblivious to ways of small web dev shops. For people who began their careers at 60k a year internships, getting into shoes of a person who does coding for 30k a year is impossible. 4. Talent flight and turnover is real. 5. This is all about really expensive quick and dirty code. 6. "The big dotcom" type of companies tried time and time again to tap into the market to extract rents, and with exception of Macrovision nobody ever succeeded. This is the reason Adobe is lobbying for unusable, unwieldy APIs in hopes of selling tooling for it.
- j45 8y agoI'd hope compiled binaries can run more efficiently than dynamically compiled Javascript over time. Right now my mobile device is often tapped by Javascript that insists on running in the background.
- Eequei3i 8y ago> decrease our reliance on particular operating systems By replacing it with a poor simulacrum of an operating system. Browser APIs are an inefficient subset of libc and bsd sockets offer. And they provide near-zero interoperability with native applications. No filesystem access (beyond the clunky save-one-file dialog), no CLI, no IPC, nothing. That means browsers are building on top of operating systems while not interoperating with them.
- throwaway2016a 8y ago> No filesystem access This is a step forward not backwards. The security model of allowing apps access to your full filesystem (assuming your user has access) is flawed. It leads to apps storing data in funny places, reading files they shouldn't, and general mayhem. Requiring the user to explicitly allow the app to access the file is a good thing. There are some use cases that are hard to support (like being able to open all the files in a folder). But people are working on a solution.[1] > No IPC WebRTC while not the same and far more overhead (due to TCP sockets vs OS level sockets) can function very much like IPC. And there is nothing stopping a process running in a different browser (or even no browser at all) to connect to a webapp using WebRTC locally. Additionally, if a new window is opened by Javascript and both pages are in the same domain + port (or subdomains of the same domain and you have access to the parent domain) you can communicate between the windows with simple Javascript function calls. And since browsers are moving towards a 1 process per window setup this is essentially IPC. > That means browsers are building on top of operating systems while not interoperating with them. While I can't argue with that. So is X Window. The abstraction between app and OS is a thick gray line not a thin black one. [1] https://developer.mozilla.org/en-US/docs/Web/API/FileSystemDirectoryEntry https://developer.mozilla.org/en-US/docs/Web/API/FileSystemD...
- TeMPOraL 8y ago> This is a step forward not backwards. The security model of allowing apps access to your full filesystem (assuming your user has access) is flawed. It leads to apps storing data in funny places, reading files they shouldn't, and general mayhem. Requiring the user to explicitly allow the app to access the file is a good thing. Most apps being limited to their little part of the filesystem is not a problem. The problem is, now as a user, I can't access those files. I can't view them in a form that suits me, I can't use other applications to operate on them. The true form of the data is forever hidden from me, a secret of the application that "owns" it.
- TeMPOraL 8y ago> Would I complain if I could run a full version of Word or Excel in the browser? The browser would become a universal interface in another way and decrease our reliance on particular operating systems. I for one would, because the browser is an absolutely shitty interface. You're still forced into "there are tabs, which contain sandboxed documents" model of use. Interoperability is nonexistant, integration with machine capabilities is superficial and completely opaque to the user, the data model is hidden (where is my localStorage equivalent of the file browser again?), everything assumes you're constantly connected - it's a corporate wet dream, but for individuals, it's a nightmare.
- j45 8y agoNothings perfect, though. If operating systems aren't, I wouldn't expect browsers to be either. Creating mobile and/or offline first exoeriences for individuals isn't a pipe dream, it was possible and happened in the 90's when connectivity (dialup) informed content (largely offline or downloaded). I'm not looking at replacement, only reasonable substitutes, which I think will become useful similar to using Google docs on mobile and web.
- yorwba 8y ago> where is my localStorage equivalent of the file browser again? The Firefox developer tools have a "storage" tab that lets you inspect the content of various databases associated with a website.
- TeMPOraL 8y agoDefault-disabled, read-only and scope-limited to domains your current tab works with, but I guess it's better than nothing.
- sidlls 8y agoDifferent psuedo-VMs, I mean browsers, operate differently even on the same specs for various technologies (CSS, JS). They already act effectively like "particular operating systems," except they're less efficient and more obnoxious to work with.
- sparkie 8y agoYou web folk are mentally ill, with the desease known as Not Invented Here Syndrome. The w3c completely detests the idea of utilizing existing technologies that don't have their name on them. Whatever the technology, it MUST be reinvented (often badly) so it can be one of their standards. I've even seen WebVR pop up recently. I'm surprised nobody has standardized a WebOffice yet, but I assume it has been put on hold because of the magnitude of the task. Can be pretty sure we'll be seeing these in the coming years: WebStore: It's silly to have Google Play and the Apple store as separate things. In future, all apps will be written in WEB and distributed from WebStore. WebCoin: Bitcoin is great, but it exists separate from the web. We find the utterly unacceptable, and we are therefore publishing WebCoin so transactions are standardized across browsers. WebPilot: Self-driving cars, IN THE BROWSER!
- sctb 8y agoThis comment breaks a handful of guidelines and is not civil or substantive. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html