Timeline for How to treat unhandled exceptions? (Terminate the application vs. Keep it alive)
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2020 at 9:08 | vote | accept | Jonas Benz | ||
| Nov 2, 2019 at 7:45 | audit | First posts | |||
| Nov 2, 2019 at 7:45 | |||||
| Oct 28, 2019 at 6:04 | audit | First posts | |||
| Oct 28, 2019 at 6:05 | |||||
| Oct 8, 2019 at 21:55 | comment | added | Mooing Duck | @immibis: Yes, Android has a large number of really low quality apps indeed. | |
| Oct 8, 2019 at 10:43 | history | edited | Doc Brown | CC BY-SA 4.0 | grammar fixed |
| Oct 8, 2019 at 9:52 | comment | added | Stack Exchange Broke The Law | @MooingDuck Plenty of Android apps (such as games) lose their state on a crash. | |
| Oct 8, 2019 at 9:30 | history | edited | sleske | CC BY-SA 4.0 | note about not overwriting |
| Oct 8, 2019 at 9:26 | comment | added | sleske | I made a small edit to note that you should not overwrite old data - hope you don't mind. | |
| Oct 8, 2019 at 9:26 | comment | added | sleske | Excellent answer - and a nice example on considering things in a broader context (in this case "how can we prevent data loss in any case of crash?") leads to a better solution. | |
| Oct 8, 2019 at 5:19 | history | edited | Doc Brown | CC BY-SA 4.0 | wording improved |
| Oct 8, 2019 at 1:19 | comment | added | Mooing Duck | en.wikipedia.org/wiki/Crash-only_software, and this is how Android apps work by necessity. | |
| Oct 7, 2019 at 18:35 | history | edited | Doc Brown | CC BY-SA 4.0 | added 355 characters in body |
| Oct 7, 2019 at 18:18 | history | answered | Doc Brown | CC BY-SA 4.0 |