Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Grive: Open Source Google Drive Client For Linux

webupd8.org

Post reply on HN
Print view View original

11–18 of 18 posts

Re: Grive: Open Source Google Drive Client For Linux

#11

Post by kijin »

ajross wrote: post #7
darkstalker wrote: post #5

A FUSE filesystem interface would be the best, so you can mount it

Difficult: the Google API doesn't seem to support random access to files, only whole downloads. So you'd need a caching layer to buffer any changes, prefetch, etc... And even then, it would be catastrophically slow for true random access. Note that even Dropbox isn't implemented with FUSE; it just watches your ~/Dropbox folder with (presumably) inotify.

Both Dropbox and Google Drive keep a local copy of all your files unless you explicitly tell them to sync selectively. Your local filesystem is the cache, so there is no need for random access to remote files. FUSE would be not only slow but also completely unnecessary for this use case. inotify is exactly the right tool for the job.

Re: Grive: Open Source Google Drive Client For Linux

#12

Post by gcr »

cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

)

Here you go. You dropped it.

Re: Grive: Open Source Google Drive Client For Linux

#13

Post by cydonian_monk »

gcr wrote: post #12
cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

) Here you go. You dropped it.

Whoops. And entirely too late to go back and edit.

Oh, the bad habits we gain from nanny IDEs.... Though most IDEs wouldn't catch it, given the ;), but would likely complain about the out-of-order ].

Thanks, though very meta.

Re: Grive: Open Source Google Drive Client For Linux

#14

Post by Arelius »

cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

You should move to California, where contracts aren't able to enforce that should you work in your own time on your own hardware.

Re: Grive: Open Source Google Drive Client For Linux

#15

Post by cydonian_monk »

Arelius wrote: post #14
cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

You should move to California, where contracts aren't able to enforce that should you work in your own time on your own hardware.

I agree. Completely.

Re: Grive: Open Source Google Drive Client For Linux

#16

Post by mparlane »

gcr wrote: post #12
cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

) Here you go. You dropped it.

Not to mention the ";)" completely messing with the matching brackets.

Re: Grive: Open Source Google Drive Client For Linux

#17

Post by rockandplace »

Arelius wrote: post #14
cydonian_monk wrote: post #3

Thank you. When the "DriveForLinux" grumbling and whining started, my response was simple: "Since when do we whine about things and not just do it ourselves?" The response I got back was mostly "because [insert excuse]." I'm not in a position where I could've done this (openly), or helped. (Contributing to open source is in a contractually grey area for me... may become my employer's property, so I avoid it. [Yeah, y…

You should move to California, where contracts aren't able to enforce that should you work in your own time on your own hardware.

Can you elaborate? What ruling was this, and how do they define "own time"?

Re: Grive: Open Source Google Drive Client For Linux

#18

Post by Arelius »

rockandplace wrote: post #17
Arelius wrote: post #14

Earlier quoted context omitted.

You should move to California, where contracts aren't able to enforce that should you work in your own time on your own hardware.

Can you elaborate? What ruling was this, and how do they define "own time"?

http://www.leginfo.ca.gov/cgi-bin/displaycode?section=lab&#3... In my limited understanding, that should allow you to continue to work on open-source projects on the side. Personally, I generally use it as leverage to get more reasonable language in my contracts at time of signage, but that seems unnecessary.
Post reply on HN