Vendor Lock-In

You cannot just go from #PERL to #Golang!!!

You should’ve gone through several DBT programmes:

#PERL ==> #PHP ==> #Python ==> #Node ==> #Golang ==> #Rust !!!

Or:

#Java ==> Java ==> #Scala ==> Java ==> Java + #Spring ==> Java #SpringBoot !? ==> #Clojure ==> Java ==> #Kotlin!!!

Joking aside: picking the right #tool for the right #problem is a #skill that can be learned “painfully” as many of us can easily continue using the tool(s) we love!

Same problem is valid for bl**dy #frameworks! I have seen first-hand how companies tied themselves to frameworks or even larger solutions based on those frameworks e.g. CMS, CRM, etc. Then they have headache for several months during the upgrade process of their systems and making them compatible with the current/stable version of the programming language or the framework!

Some examples are: #Zend, #Symfony, #Doctrine, #Drupal, #Odoo, #Django, #Angular, #StrongLoop/#LoopBack, #Hapi, etc.

We usually talk about #vendorlockin and avoiding it etc. but many of us fail to do so!

Do NOT become some people’s guinea pigs! Use light-weight frameworks if you have to. Rely on the #core, #popular, light and robust libraries of the #programming #language! Stay #AGILE!

https://en.wikipedia.org/wiki/Vendor_lock-in

Photo by Jaroslaw Slodkiewicz: https://unsplash.com/photos/SDIIfq6nhFU

Leave a Reply