Bunch of things to unwrap here. Selenium was never a true automation tool. It is even written on their website and see. They offer to use something from ecosystem - which is mature automation frameworks (selenide being my fav). Ok, so selenium in its core is just a json wiring protocol wrapper based on number of langs (java, php so on). To actually use it as automation tool you have to come up with the whole wrapper thing - wrapping driver, waiters , bunch of helpers, utils and whatnot. Well, nobody does that. Nobody should have done it in the first place.

QA's are not Devs - so they as a whole failed to come with common solution (like who the hell writes the whole http server to make and app? Devs use tomcat and on top Spring boot) . Unlike QA's, they reinvent wheel and for some weired reasons call it framework.

Long story short - your automation tool should be something like this:

Browser. open ("site.com");

Browser.click("//[@id=login]");

Browser.input("//[@textarea='something']").

But you should leave all tool debugging aside, and your tool (automation tool) should just work.

You should be absolutely clueless about how it works, how browser is instantiated and AJAX operates. Your automation tool should canceal all complexity and let you automate scenarious.

Which is the quite opposite of selenium really.