<  Back to article list

Technological Bigotry and why it’s a problem

Since the beginning of time, man has always found things to fight over: religion, sports, politics, the list goes on. And, for the most part, it has been counterproductive because it’s difficult to discuss and maintain objectivity. Not to be driven by defensive reactions in favor of their initial point of view.

In this day and age, and in the field of software development, we are being a witness to a rise of such issues. We have the OS fundamentalists always bickering over which platform is the best and keep forgetting that that is not the issue, because all of them have their positives and negatives, so saying macOS is better than Windows is, for the most part, a matter of personal preference and adjustment to the desired usage.
This kind of bigotry has caused a few casualties already. A very famous example being the slow painful death of Nokia, first by refusing to adapt to touchscreens, then not changing from Symbian to Android, then only releasing phones with Microsoft’s Windows Phone.

One of the most recent trends is framework and library bigotry. The argument “my framework is better than yours… just because it is” is being thrown around daily, and it’s quite serious because it undermines the very nature of efficient coding.

The right tool for the job isn’t a factor anymore. Developers use super bloated frameworks for simple apps just because, in their mind, it’s just better. They do no previous research to see if there’s a more apt alternative for that particular task. In fact, they not only don´t feel interested in doing the research, they are borderline aggressive if someone mentions that there might be a better option.

A very current example is the React vs Angular2 debate. While both sides have valid arguments, some people just don’t care and blindly follow a framework’s wow factor.
And while we could argue that React isn’t actually a framework (which it isn’t), to get it to function well you’d need a slew of additional libraries for various tasks. This, in essence, is a DIY framework. It allows freedom of choice (which is a good thing).

On the other hand most of these libraries aren’t backed by Facebook, so there’s no guarantee that they will be maintained. Adding to this, everyday, new and better libraries are released, rendering the previous ones obsolete, which means that people stop maintaining them.

Angular2, on the other hand, is a full blown framework than comes with EVERYTHING. From things you need to things you’ll never touch, and allows little to no freedom. But it’s all backed and maintained by Google, so developers can be relatively certain that these will be maintained.

So, in this case, Angular 2 might be suited for huge apps that need stability and will use most of the tools provided by Google. React, being much smaller and customisable, is better suited for apps that can be easily altered to include the best tools on any given month.

The truth of the matter is that it’s dumb to debate about which one is better. At the end of the day all that matters is that you’re using the best tool for the job, and the sooner the bigotry dies and people actually think objectively and rationally, the better.

Web development in particular needs to be put back on track, and that can only happen when this idiotic issue is put to rest. Let’s have a funeral on its behalf, move on, and forget this whole delusional argument ever existed in the first place.

Drops laptop and walks out the room (this was saved on the cloud, the computer is being repaired as we speak)

Miguel Pinto

Lookatitude CEO. Coder at heart. Aims to be the one who firstly opens the door for a great environment at the company, and who will ultimately drive people to share, learn and experiment.

Subscribe to Blook

Get the latest posts delivered right to your inbox.

or subscribe via RSS with Feedly!