How long since Google said a Google Drive Linux client is coming?
abevoelker.github.io
abevoelker.github.io
Why haven't they released it, if it was this close to finished? I can't say. Likely bad allocation of resources and decisions by product people. Larry is chasing Wall Street targets, which has badly slowed the pace of innovation in most of the company. The moonshots are sacred and given free reign, everyone else isn't allowed to innovate.
Blizzard had a Linux version of World of Warcraft, but can you imagine how hard it is to ensure your support staff across the world know how to handle a customer with a Linux PC?
https://github.com/xybu/onedrive-d/ (using https://github.com/mk-fg/python-onedrive)
(The usual disclaimer: I work for MS).
python-onedrive hasn't been touched in a month and since it doesn't support the new REST API, it's crippled for most purposes due to the heavy rate limits on the old API.
onedrive-d looks good but it's dependent on GNOME, making it impractical for many use cases, particularly on headless devices like a Raspberry Pi.
Microsoft has the power to support this better, why has it chosen not to?
I don't interact directly with Microsoft or Oracle, so there is not much I can complain about. Though, I've heard a lot.
Feel free to add more.
What's to stop, well, anyone from just implementing this and throwing it up on GitHub?
"Why did you do it?" "I guess I just got tired of waiting for someone else to do it for me."
On the other hand, given the size of the market for people using Linux on their desktop computers, I cannot exactly blame Google for not giving a damn about it. OTOH, Chrome for Linux exists, so...
As for the market, that includes a lot of their own employees does it not?
Edit: Not to say that there is a big market or that this would dictate what their priorities are, just saying I'm sure even some googlers would like drive to work well on Linux.
Do you mean one is not allowed to check out the code on OSX and sync to the dev/linux box?
I still bet that the majority of engineers at Google use OS X on their primary laptops (and they still wouldn't be allowed to put the code on their laptops, even if the laptops were Linux).
I asked them about OAuth token usage at one point and this was the response I got:
> The "refresh token" does not leave the user's machine. This is the permanent token that we use to generate an "access token", a transient token (expires in an hour) that is used for actually communicating with the Google APIs. We sometimes send an "access token" to our servers for verification purposes, but we never store them (and they expire anyways).
Obviously it would be better not to have to trust a third-party at all, but it doesn't seem like you have to completely hand over the keys to the kingdom.
But, trusting Google (or any company) with my data is a tough pill to swallow already, because I end up storing sensitive data, like for example I've got maybe one or two pictures of my naked wife, passwords of my accounts, backups of all emails I ever had and the list can continue. Trusting Google is one thing, but also trusting an obscure intermediary that asks for access to my data - no way. In writing this comment I couldn't even find out where they are located and this is the same story for most startups.
Also, in all fairness, if Google doesn't value me as a customer, then I'm voting with my wallet. A Linux user would have to be pretty dumb to pay Google money for Google Drive when alternatives like Dropbox exist. And to tell you the truth, I'm pretty tired of not being valued as a customer, even though I'm one of those people that pay up.
And I'm also an OS X user and frankly the OS X client sucks.
> Linux version coming mid-2015