3 ms·
"In my eyes it could be pretty nice to have a framework version that's supported for 10-20 years and is so stable that it can be used with little to no changes
by SoftTalker 2y ago
"In my eyes it could be pretty nice to have a framework version that's supported for 10-20 years and is so stable that it can be used with little to no changes for the entire expected lifetime of a system."
This is what applications used to be like, before the web and internet hit and regular or even push updating became easy.
It was simply so difficult and expensive to provide updates once the software was in the customer's hands that it was done intentionally and infrequently. For the most part, you bought software, installed it, and used it. That was it. It never changed, unless you bought it again in a newer version
- EvanAnderson 2y agoFrequent updates, in the old days, meant that a vendor had poor QA. I think that's probably still the case most of the time today, too.
- hulitu 2y agoSee Microsoft and Crowdstrike for details. /s
- tivert 2y ago> Frequent updates, in the old days, meant that a vendor had poor QA. I think that's probably still the case most of the time today, too. The internet has normalized poor QA. The bosses don't give a shit about QA anymore because it's so cheap to just push out a patch. I mean just look at old video game magazines that talked about the software development process: the developers would test the hell out of a game, then test the hell out of it again, because once it was burned onto a $100 cart (in 2024 dollars) it wasn't ever going to change. Now games can remain buggy and unstable for months or even years after "release."
- dasil003 2y agoI never worked on games, but I did do a streaming video app for PS3 in 2010, during the time period when it was arguably the best media center box available. Working with Sony (SCEE) on this was eye opening how their QA process was set up. Essentially you formally submitted the compiled app (C++ and Flash!) to them, and then tickets would come back and you'd have to address them. QA was a separate org so you never really met them in person, all issue discussion would happen in-band to the ticketing system. QA had all the power to decide when and if this thing would ship, much moreso than Product or Engineering. I can't say the process made a ton of sense for a downloadable app powered by a multi-platform online service, but it was illuminating as to how the high quality bar of 90s/00s console games was achieved.
- chrisjj 2y ago> then tickets would come back Luxury! With Nintendo you'd often get only one ticket. Any further bugs would cost you further submissions, and months of slippage.
- dasil003 2y agoThanks for jogging my memory! I believe we did two rounds of QA, the first was unlimited but shallow and high latency, the final QA I believe was called Format QA and there was a quota, if you had more than 6 issues or something you were rejected and had to go back into the queue (for months).
- specialist 2y agoaka acceptance testing aka The Correct Answer™ For the products I managed in the 90s, I put QA/Test in charge of releases. Very unusual. The results were awesome.
- numpad0 2y agoWindows XP. High profile zero day cases and Windows Update during 2000s created a "security updates are like dietary supplements" mindset.
- chrisjj 2y agoThe differece is it no longer means the vendor's QA is poorer /than average/.
- jjav 2y ago> Frequent updates, in the old days, meant that a vendor had poor QA. I think that's probably still the case most of the time today, too. Back in the 80s and 90s if you had bad QA you'd ship very buggy software and customers hated you because they had to live with it for months and months until the company managed to do another release. And then it was costly to ship off those floppies to every customer. So there was a very real price to pay, in money and reputation. Then it became possible to do updates online. Initially it was a nice way to deliver an emergency fix if necessary, but you mostly continued to do nice QA'd releases every now and then. But as with everything, when something becomes too easy it gets abused. So companies realized why do much QA (or any QA in extreme cases). Just push updates all the time and hope for the best, if customers (who are now QA) scream, push another update tomorrow. Break quick, fix quick. It's mostly unsatisfactory if one values stable quality software.
- hulitu 2y ago> So there was a very real price to pay, in money and reputation. Microsoft Corp. would like to have a word with you. /s
- hypercube33 2y agoI remember even games, or especially games were like this. Interplay would rarely have a post launch patch or make it past 1.01 versions of a whole game. then in the late 90s or 2000ish Tribes 2 came out and basically didn't even work for over a year until patches finished the game. I think once Internet hit critical mass things shifted forever and haven't gone back.
- teeray 2y agoAlso, the bugs became part of the game and make the whole thing more interesting. Speedrunning as a whole relies on these flaws.
- palata 2y ago> For the most part, you bought software, installed it, and used it. That was it. It never changed, unless you bought it again in a newer version And it was much better than the current situation, if you ask me.
- acdha 2y agoThat software did a lot less, however, and you just had to live with bugs. I knew people who just learned that they couldn’t use a feature without crashing, or had to disconnect from the internet to print, had to write their own math formula because a built in function was wrong, etc. and just worked around it for years. The first company I worked for in the 90s had a C codebase which seemed like it was half #ifdef or runtime version checks because they had to support customers who rarely updated except when they bought new servers, and that meant that if some version of SunOS, DOS/Windows/etc. had a bug you had to detect and either use a work around or disable a feature for years after the patch had shipped. I do agree that stability, especially on the UI side, has serious value but my nostalgia is tempered by remembering how many people spent time recovering lost work or working around gaps in software which had been fixed years ago. I think the automatic update world is better on the whole but we need some corrective pressure like liability for vendors to keep people from pulling a Crowdstrike in their testing and reliability engineering.
- palata 2y ago> I think the automatic update world is better on the whole I think that we went to another extreme. Because it's so easy to update, we just ship bad software saying "we'll fix it later". And we don't.