An industry standard by definition is a common way to resolve a problem.
However, corporates spend so much time attempting to standardize technology that they completely ignore the fundamentals of development as well as the tried and tested universal methods of producing a result.
While not all industry standards are bad, there is a clear difference between universal methodologies and industry standard.
Universal methodologies are usually theoretical in practice and do not change much over time, however industry standards change drastically over very short periods of time.
Why is this unproductive?
Well firstly you straight jacket yourself into a certain way of thinking. You also end up writing a lot code that is unnecessary because you are trying to work within your constraints. You are also training your brain to take a mechanical approach to programming instead of finding productive solutions to problems.
The common argument produced is that when something is standardized, that there are more people that know how to use it.
Well, this observation is actually factually incorrect.
Let us take the most common frameworks used for web development. As you can see by this link the market is fractured with small pockets of developers using each framework. However, all developers using these frameworks write the underlying languages of these frameworks. Therefore logic would state that the underlying languages are the universals.
Which is why, we focus on universals and not industry standards.
Now you could make the argument that you need a framework to produce productive code, and you would be correct, however the most productive frameworks are the micro frameworks specifically designed to produce a very specific focus to achieve a very specific result. Micro frameworks are not usually considered industry standards but tie into universal programming. They also closer resemble the core languages and are less restrictive
For example, corporates love vue.js however vue.js has a lot of weakness when it comes to things such as Augmented Reality at the time of this writing. However a micro framework specifically designed to work with Augmented Reality such as this one, makes life very simple for any developer to implement their desired Augmented Reality result.
Now you might ask the question, well why not use both?
Well the simple answer is that general purpose frameworks attempt to tackle common tasks and while they make provision for extensions and integrations, most of the time this actually slows down productivity because the integrations are usually complex as the frameworks are by definition not designed to tackle tasks that are cutting edge. If they were, well then they would be micro frameworks.
If an industry standard becomes popular and there is a better way of achieving a result, that is more productive and simpler, usually companies will force their developers to implement the industry standard regardless.
The reason for this because it is easier to market however this actually pushes up the price for the client and slows down productivity.
Micro frameworks reduce the size and increase performance of applications, resolve specific problems, reduce code complexity and bloat.
But there are very few implementations as industry standard micro frameworks are rare.
When approaching a task in a common way, you make it easier for hackers to exploit your code and thus you spend far more time securing your code.
When you are forced to use an industry standard, your application does not stand out as different, which can count negatively for marketing in many cases however there are many circumstances that this can be useful as familiarity reduces the learning curve for your users.
However, familiarity is better implemented using universal technology as your user base learning curve will have a broader reduction.
Industry standards are often trend related and thus as trends go in and out of fashion very quickly, a lot of money is spent on reprogramming these applications in order to keep up with the trends.
If one where to use universals mixed in with cutting edge technology, instead of following the trend you are defining one.
This itself has it’s own problems as often taking something new to market is not easy however your product will typically have a longer life expectancy.
This is why we at Intelligent Maps (Pty) Ltd believe in the right tool for the job and only use the most productive methods of producing results, which does sometimes does include industry standards when it is convenient to use them for a specific task