explain one thing to me, how and why is the software development given so much slack in terms of delivering quality product first time? it has become a norm to ship a new version and then have several patches/hotfixes in very quick succession, indicating that even most basic functionalities were not tested thoroughly.each and every new big release requires the same process again and introducing new bugs for every one that was fixed.when car manufacturer launches new model and after 3 years it turns out that some cars had some limited problems they usually oblige themselves to fix it at no cost. and this incident gets remembered for years to come, usually tainting the whole reputation of that given model line even years after it has been fixed. so why do people don't think that way for software products>inb4 but everyone remembers vista yeah and then each new version had similarly important problems and the trend just continues Even before internet made software distribution easy you were supposed to somehow acquire patches and patch software like nothing ever happened. developers response for why this or that doesn't work is simply just update, as if every wrong doing has been shed and redeemed by the mere effort of making it hopefully better next time.
>>108667562cause it's easy to spam updates. old software couldn't do this because you had to go to the store and buy a new floppy disk if you wanted to update your software
>>108667562>when car manufacturer launches new model and after 3 years it turns out that some cars had some limited problems they usually oblige themselves to fix it at no cost. and this incident gets remembered for years to come, usually tainting the whole reputation of that given model line even years after it has been fixed.>limited problemsNigga the kinds of recalls that cause reputational damage are always going to be life-threatening issues, things like airbags not deploying, brakes not working, etc. Are you seriously going to compare that to non-critical & usually free software shipping with some bugs?Anything that's worth a damn and is actually critical (e.g. air traffic control) are always going to be battle-hardened by competent developers. Everything else is just a playground for stupid faggots (web developers, self-taught, third worlders of the south asian variety).
Easier update delivery. That's basically it.
>>108667595>Are you seriously going to compare that to non-critical & usually free software shipping with some bugs?except that I compare it to operating systems that run everything from your mom's youtube browsing machine to nuclear plant operator stationjust because someone may associate software with neet ricing his desktop doesn't software cannot be of critical importance and I didn't word my post to mean free software only
>>108667562ESL jeet: The post
>>108668113you cant be ESL when you learn both local language and english while growing up
>>108667562it depends on the areacheck out software development at nasaor for the paris metro systemI'm not familiar with the field, but I imagine also medical stufflook at formal methods, strict subsets of a language, etc.the reason most software development doesn't follow that is that usually no one dies if there's a bug. and shipping something broken but mostly functional that will generate revenue immediately is worth it
