3 ms·
You would if their services crashed every day though right? Like when you pay to get your car fixed, there's an implicit expectation that it will be fixed well
by kraftman 3y ago
You would if their services crashed every day though right? Like when you pay to get your car fixed, there's an implicit expectation that it will be fixed well enough that it doesnt break the same way again for a certain amount of time, and it doesnt make anything else break.
If you found out that the garage was using wooden wrenches that broke 10% of the time and they passed that cost onto you, or occasionally broke and damaged the car, but didn't in your case, you wouldnt be like 'oh well, they fixed the problem, Ill keep going back to them'.
- chadash 3y agoi'm trying to think of the coding equivalent of wooden wrenches? Let's say that's an app written entirely with VBA. If I perceive that it solves my problems, then for most use cases, i'd be fine with it. I guess if it's running my bank account or it's a platform for deploying my code, maybe i'd care somewhat, but in 99% of cases, i wouldn't. But the reality is that most code is written in a language that's good enough. It's a metal wrench that might be showing some rust. Do I think that PHP is a good language to start a project with today? Of course not. Do I care if you wrote your site 15 years ago and it still runs on PHP? Not really.
- kraftman 3y agomaybe a better anology would be using the wrong tool to get something done. like you could use a high quality hammer to hammer a high quality screw into two pieces of wood, and it would probably hold them together, but you shouldn't. you could build an entire SPA in pure JavaScript...