After nearly 3 decades of HTML, CSS and JavaScript, the emergence of new device types has driven the rise and fall of frontend frameworks in breathtaking pace. Twenty years ago, the idea of the one publishing framework that would deliver all different types of document types was expected to be the next big thing. Take Apache Cocoon.
Cocoon back then employed many modern concepts of programming, like Dependency Injection or Formatting Objects, which are still on the shelf of today's hit list. But the idea of the one thing to be everything for everybody, has changed to a much conciser focus.
Frameworks now solve one main issue and help in a more orthogonal kind of way. Like Tailwind CSS, the utility framework that enables your team to craft beautiful websites without jumping back and forth between editor windows.
Tailwind supports mobile responsiveness. When your devs take responsiveness into account.
But would choosing Tailwind free you from putting a second thought into responsiveness in development?
Surely not!
Here's the thing: With the freedom of choice also comes the freedom of the domain to choose from. Even today, this often times translates to trading benefits between different possible solutions.
Your initial decisions can drive your problem domains for years – in the context of ERP up to decades.
It might be wise to choose from the number one in ERP, because this company has seen so much more than we would ever expect to see in our cozy worlds.