In the past, browser capabilities were lacking and often times not uniform or standard. JQuery a bulky library, was essential for web development and creating fluid website experiences. However, as web technologies continued to progress and conventions continued to be adopted, various browsers have created a more robust general standard for browser capabilities. Today, native browser functionality can easily offer the same experience as JQuery but with better performance.
One of the first things considered when we decided to convert our stack was choosing between between the React or Angular frameworks. In other words, choosing between Facebook or Google. This would have restricted us to more or less being followers of the current iteration of technological trend. While we are sure both frameworks are great platforms to develop on, we did not like either. It seemed more or less like picking and betting on the next web development fad. A fad which may only last for a few more years and is dependent on two, admittedly, behemoth sized corporations for upkeep and maintenance.
As a company that works with infrastructure as a platform, these options did not make much sense. From an architectural design perspective, there was also no reason to not design our platform at a lower architectural barebones level. Instead of being reliant on the next paradigm or framework in the pyramid of web development dependencies.
Not choosing React or Angular usually still means developing with JQuery and requiring a few JQuery friendly libraries dependent on various JQuery versions. We thought better. Why not remove JQuery and JQuery UI (a pretty big library) as dependencies and just go native?
We were only using a very small subset of JQuery UI but the general performance difference was enormous.
Adding and compounding all of these performance boosts made the effort for the switch more than worth it.