emu is far from leaving its state of turm oil, I wouldent expect to ever see it stop. The database is far from perfect, and never will be. Theres hundreds of unimplemented features and rewrites of existing features to be done. When the DB changes, it changes for a reason, and a standard is not going to facilitate the change. Even if a 'stable' release was tagged, it would last about a month before one of the devs put some DB changes in, which would not be in the stable branch because its 'standardized', so they go into the dev branch, and the dev branch would become what it is today... the only thing people are using because thats where all the cool shit is, and it cant be merged because it has 'db changes which break the standard'... the story goes on...
since I got here, database updates have been well documented, and scripts are provided to do anything that is more complicated.
Tools are not broken because of database changes (well, they are, but...), they remain broken because the people who release them do not release the source code for them, so they cannnot be updated by the community, or they are written so terribly or in such an obscure language that nobody else can compile them.
Databases of custom content are lost because the people who develop them follow no form or discipline in their records, and as such they cannot be integrated into future databases. Or, they approximate enough stuff to make it undesireable to use them.
|
Threaded Mode
