Large enterprise application software companies like Oracle and SAP used to have
powerful desktop applications. During the Internet boom of the late 90s, these companies
tried to provide a class of software called "self-service" where all employees, and not
just those working on back-office data could interact with the applications to perform
simple tasks. The web UI of that era was very basic and so it wasn't possible to create
desktop grade enterprise applications for the power users.
As time passed, concepts such as PPR (partial page rendering) and AJAX have helped to
push the sophistication of the UI in these web applications to the extent that these
days even the power user applications are completely delivered via the web. However
this used to be a dark art until the advent of the frameworks like Angular and React.
These days anyone can build extremely complex UI very declaratively.
This complexity on the fontend perhaps pushed the balance of the backend-vs-frontend.
While historically backend development used to be hard and meant for advanced developers
these days the complexity of the frontend also requires highly trained developers and
in some ways simplifies the complexity on the backend. No wonder, a good React developer
charges $250/hr or more these days.
In spite of all these advances, I think there is one area where things haven't really caught up
enough. That is the ability to deal with semantically displaying large amounts of data. It could be
too many rows or too many columns or both. Basically, the lack of an awesome semantic data grid.
But SQL Frames wants is making progress to change that.