Why Not Just Use …?
3 September, 2024
When you write about software (especially software of the free/open source variety), you tend to get the odd comment or three. Occasionally, that’s praise. Every so often, it’s some constructive and helpful criticism. More often than occasionally, it’s someone telling you that you know nothing or are an idiot.
Invariably, there’s always someone who pops their head in and asks Why not just use …?, followed by the name of their FOSS application of choice. As if there is (figuratively) no other choice. As if there should be no alternatives to their favourite.
Why not just use …? is a question asked from a particular frame of reference. It spawns, in no small part, from a conceit that can come from viewing things through that frame of reference.
The frame of reference I’m talking about is what works for the person posing the question. The conceit I’m talking about is that since some piece of software or another works for them, it’ll work for someone else. For everyone else.
Rarely is that the truth (universal or otherwise). Each of us is different. Each of us has different needs and different use cases. Some of use want or need more from their software. Some of us want or need less. Much less.
For many, the commenter’s preferred application might be too big or pack too many features which will go unused. Or the commenter’s preferred tool might require more setup or configuration or maintenance than others might be capable of providing. Or even want to provide.
Let’s look at class of software close to my heart: the text editor. When I write about simpler ones, I regularly hear the refrain of Why not just use Emacs/vim/VSCodium?. Those editors pack way too much for many folks. And, at least a couple of them, have idiosyncrasies — both small and not so small — that make them a tad more challenging to use. In my case (and I’m sure for others, too), the GNOME Text Editor works best because it does what I need it to do. Nothing more, nothing less.
There’s nothing wrong with having a bit of choice. It makes for a stronger software ecosystem. And if a piece of software fits the limited needs of a group of people, there’s nothing wrong with that either. On the other hand, that piece of software might not be enough for others. The twains of the two uses cases might never meet, so why should one group shoehorn their needs into something that’s not suited to them or their needs?
And, as I keep pointing out, it’s not my place to prescribe what others should use for any task. It’s not your place, either.
So, the next time you’re tempted to say Why not just use …?, take a moment to reconsider. Better yet, please keep the question to yourself.