4 ms·
I don't follow your reasoning here. If it screws up for this one meganote then it can screw n% of notes in general. The user will use some data - which is prett
by andybak 12y ago
I don't follow your reasoning here. If it screws up for this one meganote then it can screw n% of notes in general. The user will use some data - which is pretty much the one thing Evernote is supposed not to do.
Also your git analogy is a bit flawed - your argument is more like "evernote corrupted your one critical file - why don't you spread your critical information across several files?" - it hardly affects the core fact that evernote shouldn't be corrupting files at all.
- michaelcampbell 12y agoIt shouldn't, but we don't live in PollyannaWorld. > but the user also did everything in their power to make the effect as damaging as possible. This was his point. And he's right.
- kstrauser 12y agoAgain, it shouldn't corrupt any at all, and that bad is on Evernote. But I'd suspect that the odds of corruption is proportional to the size and activity of the note, and having 100 tiny notes is less likely to trigger corruption that having 1 hectonote the same size. I'm not sure why you'd ever want to do that anyway. Evernote has tags and folders to help you organize lots of bits of information in separate notes. Whatever storage system you're using, it's never a good idea to poke a stick at it and dare it to cause you pain. They generally oblige.