| |||||||||||||
Plain TextPlain TextPosted Feb 2, 2011 23:13 UTC (Wed) by jeremiah (subscriber, #1221)In reply to: Plain Text by HelloWorld Parent article: LCA: Lessons from 30 years of Sendmail
In this case, were talking remote Linux boxes on non-broad-band connections. So seriously vi is all we have sometimes. Doesn't mean I don't also have a nice GUI front end to things, when it's an option. Things are also written so that the data can be stored in a DB if the admin chooses. But the default is to assume we are in a worst case scenario, until proven otherwise. Also makes it lighter weight. Of course there is Berkley DB which is pretty light. Awe who knows. There's never a single correct solution for everyone, all you can do is make a lot of things optional, and spend a lot of time thinking about what the best defaults are for the majority of people.
(Log in to post comments)
Plain Text Posted Feb 3, 2011 17:34 UTC (Thu) by iabervon (subscriber, #722) [Link]
psql is probably even less latency-sensitive than vi (being based on readline and stdout), and is at least as good at making controlled modifications to structured data. It's not so good at changing one character in a long string in a single field, but it's great when the granularity of the database matches the granularity of the data.
|
|||||||||||||