5 ms·
20-25 years ago there was at least lip service paid to the idea of "how do we improve software quality", but somewhere along the line that got lost under "move
by greenbit 5y ago
20-25 years ago there was at least lip service paid to the idea of "how do we improve software quality", but somewhere along the line that got lost under "move fast and break things", which paved the way for "as a service" madness. I don't want your half baked junk, I don't want constant updates, I don't want monthly fees for perpetually shifting, broken crap. I don't want any ongoing relationship with a team of "devs". I want to buy it once, and if it doesn't work I want my d### money back.
- neom 5y agoIt's an interesting question, from a user perspective, would you prefer highly polishes feature rich yearly releases, or continuous feature release? Comes down to competition I guess, for web people can compete against you a lot quicker, if you think back to the 90s, Adobe could afford to take a year, no one was going to do better than Adobe anyways. Depends if the customer could understand/accept the value prop of "we're slow but good" - and if you just ship then get "good" in the wild.. well.. you may end up at the same level of baked when the other person released theirs.
- MiddleEndian 5y agoAdobe could still afford to take a year or more. I pay for CC for a project I'm working on, and in spite of the monthly fees I disable automatic updates. I don't want shit to change or break arbitrarily, I want the tools I used yesterday to behave the same as today unless I make a decision to change something.
- someguydave 5y agoThis position would make more sense if the browser and libraries and OS and hardware the users were running didn’t experience breaking changes every 6 months or have horrific vulnerabilities baked in.