Live data from Hacker News

Web Writable Files API: Simplifying Local File Access

developers.google.com

101–110 of 115 posts

Re: Web Writable Files API: Simplifying Local File Access

#101

Earlier quoted context omitted.

Am I the only crusty old fart who thinks this a lousy trend? I worry the next talented generation of developers is being alienated from the desktop, and as a result my computing experience will degrade as Chrome's piecemeal attempts to reinvent the OS leave me with an inferior selection of browser-based toys that are awkward and clunky compared to their native counterparts. I grant the browser fixes a couple things m…

But why is it always necessarily "awkward and clunky"? As always on network connection becomes more and more ubiquitous, internet connected experiences become better and better. Just look at (well-designed) experiences today like streaming video. I'm excited about things like WASM that will allow browser-based experiences to close the gap more and more with native apps. The web infrastructure is extremely powerful an…

> As always on network connection becomes more and more ubiquitous, internet connected experiences become better and better. Just look at (well-designed) experiences today like streaming video.

As not everyone even has a network connection, I find this kind of viewpoint outright dangerous because it leaves out hundreds of millions of people. Streaming video, in particular, seems to choke if you don't if you don't have the absolutely best connection.

Re: Web Writable Files API: Simplifying Local File Access

#102
post #97

Earlier quoted context omitted.

Problem with PWA: Native access, Browser versioning and seperation of processes. 1. If when you ran a .net application all .net applications shared the same parent process that'd be a significant problem. 2. Many electron clients control their versions because there are bugs, quirks, removal of features, or other changes in chromium versions. Discord last time I checked is still on 56. 3. PWA's do not have native acc…

Safari... cares about Linux?

Maybe they meant WebKit?

Re: Web Writable Files API: Simplifying Local File Access

#103
Safari 11 or 12 introduced a new extension system where Safari extensions ship as a macOS app with a Safari extension component that can communicate with the native app. And the macOS app has standard Mac Store sandboxing options (by default, no FS access outside of its bundle).

I've written some extensions for personal use and so far it's been a great trade-off.

Re: Web Writable Files API: Simplifying Local File Access

#104

Earlier quoted context omitted.

No, you can just install a self-signed unique cert for each machine.

Asking users to install a CA or cert is not a good or scalable solution.

Since when does a desktop application need to ask the user anything to install a cert programmatically? Enforced desktop sandboxing hasn't really taken off.

Re: Web Writable Files API: Simplifying Local File Access

#105
post #30

Earlier quoted context omitted.

As you surely noticed, for last 10 years the browser is actively trying to replace your desktop OS, so that the browser would become the platform, instead of Windows / macOS / Linux / anything else. Imagine the desktop becoming ChromeOS on any computer, not just Chromebooks. For this, the browser must make all the traditional OS interfaces available. It has interfaces for accelerated 2D and 3D graphics, audio, USB, p…

Am I the only crusty old fart who thinks this a lousy trend? I worry the next talented generation of developers is being alienated from the desktop, and as a result my computing experience will degrade as Chrome's piecemeal attempts to reinvent the OS leave me with an inferior selection of browser-based toys that are awkward and clunky compared to their native counterparts. I grant the browser fixes a couple things m…

Same here.

I also get to pick native development over Web whenever possible.

However many of the gigs happen to be Web based, thus here we are.

Re: Web Writable Files API: Simplifying Local File Access

#106
post #91

Earlier quoted context omitted.

Am I the only crusty old fart who thinks this a lousy trend? I worry the next talented generation of developers is being alienated from the desktop, and as a result my computing experience will degrade as Chrome's piecemeal attempts to reinvent the OS leave me with an inferior selection of browser-based toys that are awkward and clunky compared to their native counterparts. I grant the browser fixes a couple things m…

No, I hate it too. As a consumer, I wish to do my computing in my machine and not in SaaS provider's machines, having to share with them personal data when there's no technical reason to do so. I think the main driving forces on this are: 1. It's easier for computer illiterate people to use web services, since they don't have to go through an installation process. 2. It's easier for developers to support their users…

4. It's easier to justify charging a subscription to your web app customers

Re: Web Writable Files API: Simplifying Local File Access

#107
post #31

Earlier quoted context omitted.

And more than that, I honestly wonder about the motives of an advertising driven company these days. It feels like 5 years later this will come to bite us in the ass as another way of exploiting access to our computer and data. What if websites start requiring specific files to exist before allowing access?

> What if websites start requiring specific files to exist before allowing access? This is certainly going to be immediately abused for encrypted storage of persistent cookies and tracking identifiers. - If my site generates cat pics, I'll put identifiers in the metadata fields of the image format. - If my site generates markdown, I'll put identifiers in an alternate data stream (Windows) or encoded in the whitespace…

I suspect it will start with persistent login based on a file and grow from there.

Re: Web Writable Files API: Simplifying Local File Access

#108
post #80

Earlier quoted context omitted.

Just the "last 10 years"? Nah, replacing the desktop OS has been the goal of browser-makers since the founding of Netscape nearly 25 years ago.

I'd agree with the 10 year timeframe. Before that browsers were basically aiming for HyperCard. It was only after the combination of the WhatWG and the emergence of the app store as an ecosystem threat that the browser vendors have pushed the browser towards OS replacement.

Bill Gates did see Netscape as a potential threat to Windows. Java with Sun's "the network is the computer" motto as well. So yeah, people in the 90s were dreaming big. And then in the 2000s people were complaining that Microsoft set computing back by a decade.

Re: Web Writable Files API: Simplifying Local File Access

#109
post #31

One of the great things about browsers is the way you can trust them to be reasonably sandboxed from the rest of your machine. Features like this chip away at that trust model and open up new attack vectors against unsuspecting users. I get the usability benefits, but the security implications are scary. How easy would it be to trick my mother into uploading her profile picture and have the site change that file into…

And more than that, I honestly wonder about the motives of an advertising driven company these days. It feels like 5 years later this will come to bite us in the ass as another way of exploiting access to our computer and data. What if websites start requiring specific files to exist before allowing access?

You mean user name and password?

Re: Web Writable Files API: Simplifying Local File Access

#110

Earlier quoted context omitted.

Am I the only crusty old fart who thinks this a lousy trend? I worry the next talented generation of developers is being alienated from the desktop, and as a result my computing experience will degrade as Chrome's piecemeal attempts to reinvent the OS leave me with an inferior selection of browser-based toys that are awkward and clunky compared to their native counterparts. I grant the browser fixes a couple things m…

You're not alone. In another 20 years, you'll get to laugh tragically as a new generation of naive young techs invent yet another layer of abstraction on top of the browsers and gush about how this time it will finally be a universal platform. And your old 2TB of ram, 50 core cpu laptop might even still be able to run a text editor with only a few seconds of latency. And it goes without saying that, for your own safe…

With more power, comes more stacks of needless abstractions...
Post reply on HN