One of the potential issues is that companies tend to leak information. To your point, while you may not want your old fellow high school students finding you, a quick bit of data mining on your profile could probably guess fairly quickly and present your profile to those individuals without your consent. (Obviously, mileage will vary depending on how much information you've elected to share, but it's fairly disturbing how easy it can be to isolate individuals in a fairly large group off of only a few small traits.) Just look at how the Netflix Challenge data was matched to individuals based off of very meager information.
The bigger issue at hand is that when you start adding up all the various public bits of information, things can get rather scary. Did you know that in Canada, a credit card company could determine potential credit risk based off whether or not an individual bought a drink in a particular bar in a particular city with fairly impressive accuracy?
http://consumerist.com/2009/05/your-credit-card-company-is-b...
I could easily imagine that an insurance company may want to determine risk profile for customers based off of browsing history and age, or possibly an online retailer may alter prices slightly because they know you have more income to spend and a history of not checking prices that aggressively.
The larger a presence you have, the easier it is to do that sort of thing.
yep, on a daily basis. I also handle php.ini, java properties files and a slew of others. (Including the ever loving satan spawn of sendmail.cf).
All of which are simple key value pairs. Apache (and a few others) introduce scoping with psuedo XML, but again, it's not complex logic.
I brought up m4 because that was the last time someone tried to solve the configuration problem with a "simple and easy" macro language. Yeah, that worked great.
Layering Lua (or any language) as your configuration option will not simplify things. In fact, I'm willing to say that it will make it much, much harder as folks suddenly become increasingly "clever" about how they construct those config files.
I want my config files stupid. I want them heavily documented so that when I (or someone else) next has to manage them two years from now after working on multiple other projects in various languages and systems, they don't have to spend a week trying to remember what the hell this is doing, deciphering cryptic compile time errors, or wondering what the complex state machine construct someone layered on top of port allocations is supposed to be doing.
key=value is really so hard that we need to replace m4 with lua? Honestly? Before you feel the need to flame, imagine if this proposal had been for implementing the config file in COBOL (a language designed to be code readable by non-technical people). Would you still believe it to be a good idea?
What ever happened to wanting to keep things simple?
The bigger issue at hand is that when you start adding up all the various public bits of information, things can get rather scary. Did you know that in Canada, a credit card company could determine potential credit risk based off whether or not an individual bought a drink in a particular bar in a particular city with fairly impressive accuracy? http://consumerist.com/2009/05/your-credit-card-company-is-b... I could easily imagine that an insurance company may want to determine risk profile for customers based off of browsing history and age, or possibly an online retailer may alter prices slightly because they know you have more income to spend and a history of not checking prices that aggressively.
The larger a presence you have, the easier it is to do that sort of thing.