You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 3, 2020. It is now read-only.
Do NOT use this application when you're working with classmates on a project. The risk of losing data in files is way too damn high. Here's why:
The merging mechanism isn't just stupid, it's nonexistent. Have this situation:
a/
b.txt
c.txt
Have one example. It's the absolute worst one:
Edit b.txt
Drive pull a
b.txt will show an "M", stating it's modified. If you proceed with pulling, b.txt will be overwritten with an older file.
Why would you want to pull the folder? Well, your teammates might have edit c.txt, or maybe they have even edited b.txt. When you see that b.txt was modified, you're led to believe that your teammates modified it. The fact is that it could mean that, but it's probably because you edited b.txt yourself. There is no way to tell.
In a project I handed in today I was very careful to push and pull per file. Luckily no one else edited files at the same time I did, that would have put me in deep trouble. That or maybe that did happen, drive wouldn't have told me so there would be no way for me to find out unless they actually told me. Despite the per file push/pulling I still lost data, most likely because I pulled the folder thinking I had pushed my per file changes.
Files just get overwritten. Both on push and on pull. No merging, no conflict mechanism, no warnings that you're overwriting unsaved changes (or haven't merged with the latest version yet) and a downright misleading status message. This tool is not safe for projects in which people cooperate.
The text was updated successfully, but these errors were encountered:
Do NOT use this application when you're working with classmates on a project. The risk of losing data in files is way too damn high. Here's why:
The merging mechanism isn't just stupid, it's nonexistent. Have this situation:
Have one example. It's the absolute worst one:
b.txt
b.txt
will show an "M", stating it's modified. If you proceed with pulling,b.txt
will be overwritten with an older file.Why would you want to pull the folder? Well, your teammates might have edit
c.txt
, or maybe they have even editedb.txt
. When you see thatb.txt
was modified, you're led to believe that your teammates modified it. The fact is that it could mean that, but it's probably because you editedb.txt
yourself. There is no way to tell.In a project I handed in today I was very careful to push and pull per file. Luckily no one else edited files at the same time I did, that would have put me in deep trouble. That or maybe that did happen,
drive
wouldn't have told me so there would be no way for me to find out unless they actually told me. Despite the per file push/pulling I still lost data, most likely because I pulled the folder thinking I had pushed my per file changes.Files just get overwritten. Both on push and on pull. No merging, no conflict mechanism, no warnings that you're overwriting unsaved changes (or haven't merged with the latest version yet) and a downright misleading status message. This tool is not safe for projects in which people cooperate.
The text was updated successfully, but these errors were encountered: