Cars, are smelly, murderous, obs1337 industrial equipment that nobody
thinks are cool anymore. Except vaporous yuppies in SUV's
All the hip techies ride bikes to work because they are smart and know that
a lifetime of sitting behind the keyboard with no exercise will be shorter and less happy than one
with exercise.
Plus which bikes are scrutable, like Free Software.
Wouldn't it be better to use a trigger to solve the currency
issue?
I can see a couple of advantages to doing this though,
if you keep the user files in the database you could add a whole bunch
of fancy features that let users search, (or have agents search on
their behalf) for different items, soundex indexing, funky notification and monitoring systems, the list is endless and mostly YAGNI I suppose, but it sure sounds cool.
I'm guessing that this makes more sense the more integrated your
user's environment is; if they are using a smorgasbord of tools and
they are installing their own, a fancy filesystem is likely just another opportunity for mayhem. If, on the other hand you're building an integrated work environment that they are going to be working inside of fulltime, then this starts to have advantages. Although for a solution of the second kind it might be a better payoff to use some sort of persistent object storage.
Re:So Paint The ASCII Green And ...
on
Textmode Quake 2
·
· Score: 1
Setting the foreground color to green is very
easy to do on most any linux system that uses the color
console.
setterm -foreground green -background black
Slashdot Mirror
Cars, are smelly, murderous, obs1337 industrial equipment that nobody
thinks are cool anymore. Except vaporous yuppies in SUV's
All the hip techies ride bikes to work because they are smart and know that
a lifetime of sitting behind the keyboard with no exercise will be shorter and less happy than one
with exercise.
Plus which bikes are scrutable, like Free Software.
Wouldn't it be better to use a trigger to solve the currency issue?
I can see a couple of advantages to doing this though, if you keep the user files in the database you could add a whole bunch of fancy features that let users search, (or have agents search on their behalf) for different items, soundex indexing, funky notification and monitoring systems, the list is endless and mostly YAGNI I suppose, but it sure sounds cool.
I'm guessing that this makes more sense the more integrated your user's environment is; if they are using a smorgasbord of tools and they are installing their own, a fancy filesystem is likely just another opportunity for mayhem. If, on the other hand you're building an integrated work environment that they are going to be working inside of fulltime, then this starts to have advantages. Although for a solution of the second kind it might be a better payoff to use some sort of persistent object storage.
Setting the foreground color to green is very
easy to do on most any linux system that uses the color
console.
setterm -foreground green -background black
Enjoy