In <20090527163101.GG5158@cat.rubenette.is-a-geek.com>, lee wrote: >On Tue, May 26, 2009 at 10:53:25AM -0500, Boyd Stephen Smith Jr. wrote: >> >Then why do the dependencies require that a mysql server be installed? >> As I understand it: >> Because the "embedded" MySQL server is very much still a server. You do >> *not* have to start the daemon via the init script, and it doesn't >> listen on public ports, but it needs all the server components. >So it's neither embedded, nor a server. That might make it difficult >to use a central server for many users. Anyway, I don't like it. It's >something hidden from the user instead of telling them about >it. That's never a good idea. Actually, according to actual HCI studies it is often better to hide things from a user instead of telling them about it. Now, once the user starts looking for that setting, it should be available, but too many settings and too much explanatory text confuses rather than enlightens. >> >> These same issues can be hidden when using RDBMS backed, but the >> >> translations are usually much faster. >> >Both of these won't be human readable, plain text files. >> Actually, yes. KDE Configuration files are human-readable, plain-text >> files. They aren't free-form prose. For the most part they follow the >> ".desktop" file specification put together by XDG. >If you have to make so many "translations" of a configuration file >that nowadays' computers run into performance problems when doing so, >I don't consider the file as a human readable configuration file >anymore. I never said the translations were causing performance issues. I said they'd be faster with an SQL backend. That is definitely *not* the reason Akonadi wants an SQL backend. They are quite readable. Usually a translation is just changing the name/spelling of a key. But, it might be converting a value that is a list into multiple stanzas or something like that. Generally, they leave the values alone, but they are the migration path from 'old' configuration files to 'new' configuration files. >> >Try to read >> >your current kde configuration in 35 years, or try to read your data >> >from the the RDBMS you're currently using in 35 years. You'll find >> >that it won't be easy. >> I hope so. I plan on using different, hopefully better, software by >> then. >And what if you need the information stored in it? I won't. I'll export the data as I abandon that software. Actually, I'll export the data before I abandon the software so I can import it into the new software and test it. -- Boyd Stephen Smith Jr. ,= ,-_-. =. email@example.com ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Description: This is a digitally signed message part.