Brian MCallister argues quite convincingly that “Popularity, in technology, is shit. Seriously.”

He has a point. When we aim to make something popular we are doing so for reasons of ego, and therefore attempt to compromise what it is we’re trying to achieve. We can’t do complex and useful to niché audience if we’re worried about being popular.

One version of this internal corruption of objectives is sometimes known as the “What would your mother think?” test in development. Would your (presumably technically illiterate, possibly senile) mother make of the gizmo you’ve just made? If the answer is “she wouldn’t understand it” then the trend is to simplify and to make things better.

But your Mum probably doesn’t care about your widget. What’s more useful is whether the people who are going to use it can. And that’s why, so the argument goes, that commons-based peer collaboration might be a better design practice than what we currently do.

It’s also why I think the future of innovation in software is going to be governed by companies making money whilst putting the source code out into the open. They quietly execute, iterating out improvements, making things better with each step, and then eventually the larger market catches on. The market catches on quicker if the source code is out there, resulting in better revenue streams.

Alas, we’re still in an age where the “intellectual property” myth still permeates our society, and trying to produce popular software seems more important than producing useful software. Sometimes it’s like the last decade was a dream…