If I went through and tried to document every different concern my rails app handles, I 'd probably just give up after a few days of research and a list of thousands upon thousands of concerns.
Spice racks don't need to change and evolve over time, a third party can't remotely ruin your life if your spice rack has a design flaw, your spice rack can't make you millions of dollars.
So I get that this guy wants to go write tcp/ip stacks from scratch to build his neopets page or whatever but it's the wrong design decision for a vast, overwhelming porportion of projects.
"Spice racks don't need to change and evolve over time" => why not hold some other stuff? maybe add something to hold fruits later?
"a third party can't remotely ruin your life if your spice rack has a design flaw" => have you protected your spice rack against children playing with it?
"your spice rack can't make you millions of dollars" => depends on you, not on the rack itself
"but it's the wrong design decision for a vast, overwhelming proportion of projects" => really depends on the person doing the code and who will do the future maintenance; updating a framework that evolves fast can sometimes be as hard or harder than maintaining your own code, it's mostly a choice of the developer/development team to make on how they see things going from now
> why not hold some other stuff? maybe add something to hold fruits later?
What?? No. I have a fruit bowl and a fridge drawer to hold fruit. Why would I want to glue them together? So I can use precious refrigerator space to hold my cayenne powder? Maybe I can add a cell phone to my vacuum cleaner next, attach a paintbrush to my broom, or combine a lawn mower with a trowel.
These things do not belong together. I appreciate the vendor would like more of our kitchen storage spending, but that’s his problem, not his customers’.
These are all devils advocate answers. None of these are things I would spend a lot of time pondering if I was building a spice rack with the exception of #2 if I had kids which is solved with a single extra screw or a single piece of 3m style adhesive strip
How many people spend their free time modifying their spice racks. I'm sure you can find some webpage of someone who has this as a hobby but let's go with less than .01%
> Spice racks don't need to change and evolve over time
Your cooking may change to require more spices than it did before, exceeding the functional capacity of the rack. Change in circumstance may mean you now need a mechanism (e.g. door) to block direct sunlight from hitting the jars. Spice theft may become an issue, requiring heightened security. Or your preferred spice brand might make a seemingly minor change to the shape of their jars which cause them to no longer fit in your rack.
Again all devils advocate kind of stuff. No one who is not an industrial engineer spends time actually doing any of this stuff and the analogy is about making your own.
You could think about these things. But no one does. Necause I can buy a spice rack for $20 at target and then throw it out and buy a bigger one for $30 if that one is insufficient.
A spice rack has to do two things
1) hold spices
2) Not fall apart
3) optional : try not to look terrible
If I went through and tried to document every different concern my rails app handles, I 'd probably just give up after a few days of research and a list of thousands upon thousands of concerns.
Spice racks don't need to change and evolve over time, a third party can't remotely ruin your life if your spice rack has a design flaw, your spice rack can't make you millions of dollars.
So I get that this guy wants to go write tcp/ip stacks from scratch to build his neopets page or whatever but it's the wrong design decision for a vast, overwhelming porportion of projects.