4 ms·
This UI solves a problem for the computer, not the user. Whenever you find yourself making a UI like this, you should go back and change your program so the co
by panic 9y ago
This UI solves a problem for the computer, not the user. Whenever you find yourself making a UI like this, you should go back and change your program so the computer doesn't have that problem any more. In this case, there's surely a way to write files quickly enough while still maintaining user privacy -- just do that instead of bothering me with a wall of text every time I save a file!
- JohnBooty 9y agojust do that instead of bothering me with a wall of text every time I save a file! I certainly wouldn't want to be hit with this wall of text every time I save a file. I was thinking that this sort of option ought to be a global setting that could perhaps be altered on a per-document basis if (and only if) the user cares to muck about with it. It could, perhaps, be a choice that is presented to the user upon new document creation. This UI solves a problem for the computer, not the user. [...] In this case, there's surely a way to write files quickly enough while still maintaining user privacy Life is full of these choices. There's a gas pedal in my car. I can mash it (to go fast but burn a lot of fuel) or be gentle with it (and save gas, but I won't go as fast). Ideally the car should be crazy fast and crazy safe and crazy fuel efficient no matter how you drive the sucker, but that's a tough engineering challenge and ultimately we (today) leave that choice to the drive. That said, you are 100% correct. Maybe the privacy/paranoia steps are something that could be done on a background thread. The file could be saved quickly, and then the database could be privacy-optimized in the background immediately thereafter.