4 ms·
This is assuming that those who make rails are master chefs. This is debatable. Also, the analogy does not hold well because at a sushi bar, the one who orders
by protonfish 14y ago
This is assuming that those who make rails are master chefs. This is debatable.
Also, the analogy does not hold well because at a sushi bar, the one who orders is the end consumer. Rails is a tool for developers so a more accurate metaphor would be I am the chef, my customer orders omakase and Rails supplies all my tools and ingredients. If those tools and ingredients are what I need to make my customer happy, then great. If not, then I'd prefer to throw them away and do it right instead of dogmatically defending my framework like it's a religion.
- sergiotapia 14y agoWho would you consider 'master chefs'?
- protonfish 14y agoGood question. Web development has been around for only about 20 years and changed significantly during that time (CSS, JavaScript, Ajax.) Cooking has existed for thousands of years so I would argue that there has not been nearly enough time for any master chefs to come into being. That does not mean that many (mostly due to Dunning-Kruger) will claim to be masters and that even more will rush to the charlatans hoping for a magic spell that makes complex, new and continuously emerging technology easy without the need to learn or practice.