Earlier quoted context omitted.
> but not segmenting the market is not one of those; rather, it's a consequence of not selling the software itself. Consequence or not, how can it not be an advantage?
Because market segmentation in itself, as a concept, is not a disadvantage, which means that lack of it is not an advantage in itself. Like I said, market segmentation in software does not necessarily have to be a bad thing. Consider a hypothetical text editor that comes in two editions. The "basic" edition has features like syntax highlighting, regex search and replace, etc. The "advanced" edition has a feature that…
In your text editor example, the author can add an SFTP feature, but once it's coded it's coded. There's no extra cost to ship out all software with that feature after it's coded, except perhaps some extra support costs. (I imagine those would be pretty minimal.) At that point, I only see two reasons to segment the market from the users' perspective:
1) To not confuse your less advanced users with more features. This is a pretty weak reason, IMO. 2) To make sure that the people who actually wanted the feature are the ones paying for it. After the cost of development is paid for, this reason goes away.
Beyond these reasons (unless I'm missing something, which is entirely possible), releasing different grades of software just hurts your users. It makes you more money, though, so maybe that's enough justification.