Google Drive Desktop – A cross-platform Google Drive desktop app made w Electron
github.com
github.com
Nothing against the developer as they may be trustworthy and honest, but don't make the mistake of assuming that someone bold enough to put out something that requires that much trust must by extension be worth trusting. People too often do.
The repository doesn't include all of the code that gets included in the app, because it has dependencies. It links those dependencies on the github page, but you have to verify that the dependencies being linked to are the ones the build actually uses. Then check that you like what's in those dependencies. At first glance, a forked version of one of the dependencies is pulled from his own repository instead of the repository linked on the page, so you have to make sure you aren't vetting the wrong repository. Then the release archives package in Electron for you, so that's another thing you're trusting if you don't build it locally.
It doesn't mean anyone is doing anything wrong, but even if they have good intentions good people pull in bad dependencies occasionally too.
Developers as people are innocent until proven guilty. Software is guilty until proven innocent, especially if there's a higher chance of a security risk. Not everyone can assess that well for themselves.
Done and done. Thank's for the heads up.
> The repository doesn't include all of the code that gets included in the app, because it has dependencies.*
> Software is guilty until proven innocent
I'm not saying you're wrong about any of this, and I don't trust this app myself (mostly because JS dependencies are hard to trust for various reasons), but...
I also can't think of any usable app that meets your criteria for trustworthiness, including some made by Google itself.
At this point, building much of anything requires standing on a teetering tower of dependencies that users can't and won't audit.
The question becomes where one draws the line. I think drawing the line at "anything that touches my Drive files" is reasonable, but we (meaning computer users) spent decades downloading sketchy executables for our Windows PCs. Although many things are browser-based now, many of us still do download native executable freeware from the web.
If you think I'm not offering a better perspective, it's because I'm not. You're right, but total security also currently means using very little of the software that's available to us.
On the other hand, I download all sorts of random crap on my iPad because the security model won’t let apps do anything to shady without you giving it permission.
This is sadly not a valid comparison. Our PCa have a far more critical role in our lives now, have far more power to hurt us, and are reachable by 1000x more malicious actors.
We are in a new, dangerous world. We need much better OSes with much stronger sandboxing for our modern world.
A user with a basic habit wouldn't need to know how to read the code for this, because there are enough signals that you wouldn't need to get that far to decide not to use it.
Electron is known to be affected: https://github.com/electron/electron/issues/22346#issuecomme...
The author of Google Drive Desktop seems to be aware but I do not think anyone can win this race against Google: https://github.com/alexkim205/Google-Drive-Desktop/blob/bd9f...
But in practice, I realize I'm addicted to tabs. When working on 3 documents at once, I want them in separate tabs in the same window -- not 3 different windows.
Maybe I'm in the minority, but I'm actually at the point where I want things to go in the opposite direction -- just turn all my apps into tabs. (Like Chromebooks, I guess.)
Finder? VLC? Word? Preview? Spotify? Photoshop? My code editor? I just want them (or each document in them) as tabs next to other webpages and/or each other. (For Photoshop and code, I'll probably organize my own window/space for them, but still open up webpages next to my images/code.)
Having tabs and a dock feels redundant in 2020, like two competing paradigms that just need to be refactored into one by now.
And then each tab is an app or app document window. So I could have a Chrome tab next to a Firefox tab if I wanted. Browser tabs would be peers next to other apps.
None of this is about security, or running apps in the browser. Just using tabs as the main concept for everything, rather than windows.
There's no elegant way of telling Firefox to never use tabs, always open a new window. There are some extensions pretending to this, but the experience is terrible. There actually is a new tab created which is then detached.
I don't usually use Chrome, so I looked up wether it handled this, but it seems to rely on extensions too.
Qutebrowser works, but it has other limitations, such as poor extension support.
I've settled on NoTabs Firefox with a userChrome.css that hides the tab bar until Firefox someday supports native no tabs.
It's funny, my version would probably just put every browser tab into a different window and just use a powerful window manager like i3 to deal with everything.
These should at least get you pointed right.
Using two large monitors is bad for your neck.
One of the examples on their website groups all Adobe applications in tabs.
Microsoft also tried to build this into Windows but eventually gave up (https://www.theverge.com/2019/4/23/18512250/microsoft-window...)
Now I'm starting to think how feasible it would be to embed other desktop apps that people have installed into an electron window or something.
View/modify PWA manifest on web-app/shortcut export
Then they put a fairly conventional window manager and taskbar/dock around those in 2012, https://www.theverge.com/2012/4/26/2978163/aura-chrome-os-ha...
What's additionally weird is that you can pull your tabs apart into separate windows to replicate this exact behavior. It's hard to justify why I need an exclusive browser just for one app. For Play it's justified because of tighter integrations with the OS playback keys that the browsers historically have been flaky with, especially when you're using other apps.
In my mind, "Google drive" is storage, "Google docs" is word processing / spreadsheets etc. I have no idea why they brought docs into drive.
I don't find Google's official use of Drive and Docs confusing (there are some overlaps, but in a natural way).
In your mind is correct. Docs isn't part of Drive. The umbrella term is G Suite (previously Google Apps), not Drive.
I suppose that’s on-brand for an Electron app.
Snark aside, FFmpeg is your friend and a 1-liner plus a <video> tag will reduce this to less than a MB. Your mobile visitors will thank you!
Another alternative on Windows is to create a separate chrome profile and then create a desktop shortcut to that profile. Set the default page to be your drive in that profile
Here's an example shortcut "C:\Program Files\Google\Chrome\Application\chrome.exe" --profile-directory="Profile 2"
Use that profile as your Drive app
"Backup and Sync" still misses features like Files On-Demand/Smart Sync available in OneDrive/Dropbox and deleting files online pollutes the local trash/recycle bin on macOS/Window computers.
"Drive File Stream" actually has these lazily loaded file placeholders, but it is treated like an additionally mounted volume instead of a local folder somewhere on my local disks. It also managed to occupy over 60 GiB RAM for over a week during its initial sync which had lots of small files created by Arq Backup.
It seems like 'unlimited' cloud storage is foremostly limited by the performance characteristics of their sync clients.
It started syncing and just couldn't stop.
I had to delete or move all the Backup and Sync contents across my devices to get to 0 before it quit endlessly thrashing.
Dropbox is the best at crawling a very complex directory structure with millions of files and diffing it efficiently with the server and other clients, and then transferring all the individual changes. Nothing else comes close. And their write-ups show the work involved:
https://dropbox.tech/infrastructure/rewriting-the-heart-of-o...
https://dropbox.tech/infrastructure/-testing-our-new-sync-en...
But also throughput is good.
Also its UI (IIRC written in Python) often fails to load (give you a blank box).
Their blog posts explain why they're so much better:
https://dropbox.tech/infrastructure/rewriting-the-heart-of-o...
https://dropbox.tech/infrastructure/-testing-our-new-sync-en...
Performance will be similar to using Google Docs on Chrome. Memory usage will be probably worse since you are running another engine besides your browser.
Is it just for the convenience of not having to type the URL on your browser?
(e.g. on a plane, if I ever take one again...)
Well first of all, I'd pretty much rather have a shortcut that can be opened in any browser I'd want to use, than to download another copy of Chrome dedicated to running the Google Drive web app as its own 'app' using Electron.
Secondly, Chrome supports grouped tabs which allows you to organise your tabs anyway which sounds great over having 3 - 4 separate Electron apps trying to behave like MS Office (Just don't).
And last but not least, Unlike MS Office, this requires a persistent internet connection to function. So if your internet is down, your wonderful Google Drive electron app will look like this: [0]
[0] https://twitter.com/rhysforyou/status/1260361296551178240
There was something similar for gnu+linux too (nativefier was the name iirc) that worked for a while but then stopped working.
It was very handy.
I kind miss those things because having certain websites in their own apps within their own browser was comfortable.
EDIT: I've tried https://github.com/jiahaog/nativefier and it seems to be working again. Basically you can invoke it and pass it the url of any webapp and it will package an electron-based browser that loads your webapp on startup.
ok
If you have a setup you like, save it a shell script. You'll have to rerun as google breaks it every six months or so.
If you have not yet looked at rclone, it's worth exploring, they do a great job.
I wanted to do something like this for years, but never got the time to make it, so I'm glad to see someone did it.
However now I think this is not really relevant, thanks to PWA there's a better way to make Google docs apps feel native.