Maybe Dave Chalk could fill the void.
"Today we're reviewing a tablet PC. They're the wave of the future and come with nifty pointy-sticks. Don't worry if this all sounds too technical, we'll explain more about pointy-sticks after the commercial break."
I'm going to reserve judgment until I actually see one of these in action, but I suspect that the marketing team might hit their demographic better if they include a built-in Jolt Cola dispenser.
The problem with TCO reports...
on
Linux Is Cheaper
·
· Score: 1
I am by no means an expert (is there an acronym for that?), but how can TCO reports be taken seriously? They're usually heavily biased and omit important factors. For example, why do I almost never see the cost of downtime factored in? It would also be good to see a dollar value for knowledge management included. What I mean is, some platforms are better suited for documenting miscellaneous procedures, DB schemata, maintenance schedules -- things that are specific to an existing deployment. If my Sys Admin gets hit by a turnip truck, how quickly can his knowledge of that deployment be passed to someone else? What is the cost associated with the ability to recover quickly from something like that?
Slashdot Mirror
Maybe Dave Chalk could fill the void. "Today we're reviewing a tablet PC. They're the wave of the future and come with nifty pointy-sticks. Don't worry if this all sounds too technical, we'll explain more about pointy-sticks after the commercial break."
For the love of God, please replace it with anything other than another "Robot Wars" type of show.
I'm going to reserve judgment until I actually see one of these in action, but I suspect that the marketing team might hit their demographic better if they include a built-in Jolt Cola dispenser.
I am by no means an expert (is there an acronym for that?), but how can TCO reports be taken seriously? They're usually heavily biased and omit important factors. For example, why do I almost never see the cost of downtime factored in? It would also be good to see a dollar value for knowledge management included. What I mean is, some platforms are better suited for documenting miscellaneous procedures, DB schemata, maintenance schedules -- things that are specific to an existing deployment. If my Sys Admin gets hit by a turnip truck, how quickly can his knowledge of that deployment be passed to someone else? What is the cost associated with the ability to recover quickly from something like that?