4 ms·

I have to go with the article's position, though - I'd rather have the few seconds data loss and get the better responsiveness and a longer-lived device.

by vacri 10y ago

sdenton4 10y ago
It all depends which few seconds of data are lost, though, right? Do you just lose a new contact, or corrupt an essential database?
- kogepathic 10y ago
  > Do you just lose a new contact Are people creating new contacts that often on a phone? I probably do that only a few times per week. If the phone crashed immediately following the input, I'd just ask the person for their details again. > corrupt an essential database? It would only corrupt application data. Android isn't completely stupid, /system is mounted read-only on every Android phone I've ever seen. I guess it depends on how highly you depend on application data remaining consistent. Presumably the corruption would only apply to data that was modified but had not been flushed to flash before the power cycle, so at rest data shouldn't be affected.
  - jcheng 10y ago
    > at rest data shouldn't be modified If your data is kept in a SQLite database or any other type of compound storage scheme it's entirely possible to lose data that wasn't being modified, due to corruption of the metadata that governs the layout of the file (actually I don't have experience with SQLite file format specifically, but I ruined my startup's launch a decade ago with almost identical reasoning--thousands of pressed CD-ROMs in the garbage).
  - Sean1708 10y ago
    > I probably do that only a few times per week. Look at Mr. Popular over here.
- piaste 10y ago
  > Do you just lose a new contact, or corrupt an essential database? How essential are we talking about here? What I mean is, your smartphone is a device that can get lost, stolen or destroyed any day. All the data that is physically stored in it should either be expendable or synced elsewhere.
  - cbr 10y ago
    Something could be corrupted and then that corrupted data could be synced to the cloud, trashing what you had there.
c3833174 10y ago
>longer-lived device. Define longer-lived, you'll probably have replaced the battery several times before flash wear becomes an issue

I have to go with the article's position, though - I'd rather have the few seconds data loss and get the better responsiveness and a longer-lived device.

by vacri 10y ago

I have to go with the article's position, though - I'd rather have the few seconds data loss and get the better responsiveness and a longer-lived device.

sdenton4 10y ago

It all depends which few seconds of data are lost, though, right? Do you just lose a new contact, or corrupt an essential database?

kogepathic 10y ago
> Do you just lose a new contact Are people creating new contacts that often on a phone? I probably do that only a few times per week. If the phone crashed immediately following the input, I'd just ask the person for their details again. > corrupt an essential database? It would only corrupt application data. Android isn't completely stupid, /system is mounted read-only on every Android phone I've ever seen. I guess it depends on how highly you depend on application data remaining consistent. Presumably the corruption would only apply to data that was modified but had not been flushed to flash before the power cycle, so at rest data shouldn't be affected.
- jcheng 10y ago
  > at rest data shouldn't be modified If your data is kept in a SQLite database or any other type of compound storage scheme it's entirely possible to lose data that wasn't being modified, due to corruption of the metadata that governs the layout of the file (actually I don't have experience with SQLite file format specifically, but I ruined my startup's launch a decade ago with almost identical reasoning--thousands of pressed CD-ROMs in the garbage).
- Sean1708 10y ago
  > I probably do that only a few times per week. Look at Mr. Popular over here.
piaste 10y ago
> Do you just lose a new contact, or corrupt an essential database? How essential are we talking about here? What I mean is, your smartphone is a device that can get lost, stolen or destroyed any day. All the data that is physically stored in it should either be expendable or synced elsewhere.
- cbr 10y ago
  Something could be corrupted and then that corrupted data could be synced to the cloud, trashing what you had there.

c3833174 10y ago

>longer-lived device. Define longer-lived, you'll probably have replaced the battery several times before flash wear becomes an issue