Today's Internet Browsers are and have been rubbish. It is unacceptable to have Internet Browsers increase R.A.M. consumption. The Web Design on most Web Sites makes it impossible to navigate. Error Messages are worse than ever. They actually have Mascots (!) that dance around all the time.
Well, the root cause of the problem is that Web browsers are expected to serve as an entire OS unto themselves at this point. In order to be compatible with every Web application possible now, browsers have to support an entire scripting language (JavaScript), a video player, multitasking (tabs), a database server (Web Storage), a drawing API (<canvas>), and more. Much of that functionality is redundant with the OS's own windowing system and drawing API.
The upside means that we have a lot of functionality available that doesn't care what kind of device or operating system you're running now. So many things that were long ago executables that you had to install locally run through the Web browser now. But the downside is that supporting all of that functionality takes a
hell of a lot of RAM. If you try to use a browser with the same resource footprint of Netscape Navigator 4.08 you might be able to access Wikipedia and AARoads and that's it. It just wouldn't support enough features to handle anything more complicated.
Does that mean I have to rewrite a report at work? It uses SQL Server Reporting Service, which doesn't work with Chrome. The job that produces the report sends out an email to the users notifying them to look for it. Part of that email is a line that says they must use IE, Chrome doesn't work.
Occupational hazard of tying yourself to a non-open-source software stack, unfortunately. A less-fragile way of going about it would have been to do all that functionality in Python or Perl and have that query the SQL server using, well, SQL.