3 ms·
> but as far as the long tail goes, the kids are much less resistant to new ideas I think that the "old farts" resist "new ideas" mostly because they aren't re
by beagle3 14y ago
> but as far as the long tail goes, the kids are much less resistant to new ideas
I think that the "old farts" resist "new ideas" mostly because they aren't really new, and they know where those ideas went the last time around. You know, "fool me once, shame on you, fool me twice...";
An example: Object Oriented Databases; when they were popular (early nineties), all the "cool kids" thought the "old farts" were just resisting the "new idea", when in fact the "old farts" had experience with earlier network/entity databases (some of which weren't far from the object databases of the day), and knew why they preferred the relational databases to everything else.
For a modern example: I don't know anyone experienced with HPC who like hadoop. You pay about 10 times (CPU, management costs) for using hadoop compared to actually solving the problem at hand - in return for getting the code to a working state twice as fast (e.g. 6 months without hadoop == 3 months with hadoop). If your problem scale is small, it might seem like a win, but it isn't; If you need 10 servers instead of one, you paid ~$10000 and another month in system administration without noticing. You might still come out ahead, depending on your constraints, but it isn't clear cut.
When you're running 1000 servers instead of the 100 you could have, that's easily a couple of million dollars, which is disastrous for many projects -- and yet, I get labeled "old fart" for not embracing hadoop.
edit: minor edits