The link doesn’t talk about the SAAS model, which is probably the most profitable (and ubiquitous) one these days. I know people like to rail against it, but I actually like the SAAS model. It keeps incentives aligned. It used to be that I might shell out $200 for a piece of productivity software. Now, I might pay $10 a month instead. The thing is that under the old model, a company was incentivized by make a sale bu…
I feel it's the opposite. The incentive is to lock you in and provide as little value as possible for as much money as possible. Get you hooked, take your data hostage, and then jack up the price as much as possible while delivering little to no additional functionality. Bugs? who cares. Broken functionality? No big deal. You are locked in baby!
A world where people pay for software
61–70 of 543 posts
Re: A world where people pay for software
#62Earlier quoted context omitted.
Plenty of people are using copies of Word, Powerpoint, and Excel 2003 just fine, which received literally zero 'maintenance' for at least a decade or more depending on personal preferences. For most software that can be sold in a box, without an attached cloud service, this approach works. EDIT: Also some fraction would be using them on computers that literally haven't been upgraded or connected to the internet for a…
if you think those aren't receiving maintenance you're not paying attention or are ignorant as to how hard it is to keep a complex app compiling as operating systems move forward. Not receiving new features is VERY different from not receiving maintenance. It is wholly implausible to believe that there has been zero energy spent on keeping those codebases working in the past 10 years.
Office 2016 is going EOL in two years.
That's from Microsoft themselves. They do not hide these facts or make it hard to find.
Re: A world where people pay for software
#63Earlier quoted context omitted.
Making an excellent product is hard, but what is really hard, is maintaining it for years and decades afterwards. Maintenance, addition of new functionality, bugfixing, porting to other platforms etc. takes easily 10x-50x time than the initial release, and eats the vast majority of the developers' time and energy. This is where "not being paid for your work" translates into abandoned projects.
Plenty of people are using copies of Word, Powerpoint, and Excel 2003 just fine, which received literally zero 'maintenance' for at least a decade or more depending on personal preferences. For most software that can be sold in a box, without an attached cloud service, this approach works. EDIT: Also some fraction would be using them on computers that literally haven't been upgraded or connected to the internet for a…
Re: A world where people pay for software
#64The link doesn’t talk about the SAAS model, which is probably the most profitable (and ubiquitous) one these days. I know people like to rail against it, but I actually like the SAAS model. It keeps incentives aligned. It used to be that I might shell out $200 for a piece of productivity software. Now, I might pay $10 a month instead. The thing is that under the old model, a company was incentivized by make a sale bu…
I feel it's the opposite. The incentive is to lock you in and provide as little value as possible for as much money as possible. Get you hooked, take your data hostage, and then jack up the price as much as possible while delivering little to no additional functionality. Bugs? who cares. Broken functionality? No big deal. You are locked in baby!
There there's even less incentives to fix bugs, fix broken functionality and god forbid new functionality.
Re: A world where people pay for software
#65Besides being sick of subscriptions for every small thing, I'm not sure I understand the premise here: "Pay to download or for other services: Not worth it; users can find the software somewhere else and they don't need your other services." So users won't pay a one-time fee, but instead they will pay a subscription to get that one software they need? They won't "find the software somewhere else" if it's behind a sub…
The thing is that this solution scales better. If you had to pay all developers individually, that would not be worth it but with my solution, you have to pay only one. Also, it doesn't have to be a subscription. The payment is 100% up to the developers that you pay, so they could sell a one time payment and register a lifetime subscription in this system for that.
Re: A world where people pay for software
#66Speaking of software business models, I like the idea of charging money for convenience. As in, make the app open-source, but sell compiled binaries and maybe tech support.
Take a free open source product, and charge for hosting & maintaining it.
Re: A world where people pay for software
#67Earlier quoted context omitted.
Plenty of people are using copies of Word, Powerpoint, and Excel 2003 just fine, which received literally zero 'maintenance' for at least a decade or more depending on personal preferences. For most software that can be sold in a box, without an attached cloud service, this approach works. EDIT: Also some fraction would be using them on computers that literally haven't been upgraded or connected to the internet for a…
Microsoft also makes Windows, and Windows takes backwards compatibility very seriously. Even if they don't work on maintaining Office 2003 directly, they indirectly work very hard making sure every subsequent version of Windows does not break Office 2003.
Re: A world where people pay for software
#68Earlier quoted context omitted.
Plenty of people are using copies of Word, Powerpoint, and Excel 2003 just fine, which received literally zero 'maintenance' for at least a decade or more depending on personal preferences. For most software that can be sold in a box, without an attached cloud service, this approach works. EDIT: Also some fraction would be using them on computers that literally haven't been upgraded or connected to the internet for a…
if you think those aren't receiving maintenance you're not paying attention or are ignorant as to how hard it is to keep a complex app compiling as operating systems move forward. Not receiving new features is VERY different from not receiving maintenance. It is wholly implausible to believe that there has been zero energy spent on keeping those codebases working in the past 10 years.
This is in fact how all software worked until, I don't know, about two decades ago? Things being patched was a big deal, a voluntary manual process, and didn't happen often. The update would even have a well-known name like "Service Pack 2".
The idea that all software must be constantly maintained is recent and the assumption that it is necessary is mostly self-imposed by the software business. Users don't share this assumption, and in fact on many products, updates are viewed mostly neutral to negatively, other than perhaps critical security updates on products that are used in connection to the internet or untrusted data.
Re: A world where people pay for software
#69Software has no marginal cost. You can make something that's used by untold millions of people. Even if many people pirate enough people won't for you to recoup your development cost and then some. Software is easier to produce, sell, and distribute than any physical product. You don't have to worry about warehouses filled with unsold inventory. You don't have to worry about quality control and returns. It still blow…
Re: A world where people pay for software
#70Software has no marginal cost. You can make something that's used by untold millions of people. Even if many people pirate enough people won't for you to recoup your development cost and then some. Software is easier to produce, sell, and distribute than any physical product. You don't have to worry about warehouses filled with unsold inventory. You don't have to worry about quality control and returns. It still blow…
Making an excellent product is hard, but what is really hard, is maintaining it for years and decades afterwards. Maintenance, addition of new functionality, bugfixing, porting to other platforms etc. takes easily 10x-50x time than the initial release, and eats the vast majority of the developers' time and energy. This is where "not being paid for your work" translates into abandoned projects.
Engineering projects usually have a finished state. Software engineering is no different, no matter how much the industry wants you to believe otherwise.