Hacker News new | past | comments | ask | show | jobs | submit login

Good question. Seems a pretty simple solution: the browser is the editor, even if the files are local. We use browsers to interact with local files all the time, for example during local web app development.

Only that's impossible as it is now (and will be for the forseeable future) because it wouldn't be very wise to give browser apps write access to the local filesystem.

You would not need to be able to edit the offline file. Instead it could still be just a link to the online version of the file, like it is now. But additionally it could contain the actual data that can be imported back to Google servers when it is accidentially deleted from the server.

I was replying to the part where "even if the files are local" i.e. not on the net.

The google drive already has access to the local filesystem, so that is a not a good reason to not have a local copy of the data.

Isn't it the Google Drive application that updates those files?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact