3 ms·
This quote from http://erights.org/e/StateSerialization.html http://erights.org/e/StateSerialization.html has always stuck in my mind: Do you, Programmer, take
by panic 8y ago
This quote from http://erights.org/e/StateSerialization.html http://erights.org/e/StateSerialization.html has always stuck in my mind:
Do you, Programmer, take this Object to be part of the persistent state of your application, to have and to hold, through maintenance and iterations, for past and future versions, as long as the application shall live?
- Erm, can I get back to you on that?
- 0xcde4c3db 8y agoSee also: configuration file formats. Outside of systems where configuring the installation is basically part of the sales process, you will probably have at least a handful of customers raising hell if version 10.0 doesn't seamlessly run with a config file from version 1.0. And maybe even vice-versa.
- repsilat 8y agoAn upside to SAAS, I guess -- if the user data lives on your servers in a reasonably structured format you can try to migrate it, and your migrations don't have to work across too many versions if that's difficult (unlike file format compatibility, which is a long term commitment.) Of course, that only works to a certain extent. Removed features can't be "migrated" cleanly, and often config files (or worse -- code written by users in most DSLs) aren't well-structured enough to make migration straightforward.