Fully agree.
Its the non stop desire of js jockeys (sorry, web developers) to have a web site act with all the power of an app - go away, I want your web site to have as little access to my system as possible & that includes trying to "fingerprint" .my browser)
Personally I would like to see complex stuff in an app, not on a web page.
I would like web pages to be nice and simple & I don't want lots of insecure functionality such as a browser accessing a USB device (FFS, that is deranged - Chrome, I'm looking at you).
.. Happily for me, lots of web sites already fail by default as I have most js off by default, and if a web site does not give me anything useful with js disabled then I don't visit it in future (as js is a huge security risk, and I enable it with caution)
Seen too much i the way of crappy sites, be it XSS vulnerable through to a while ago when lots of sites went to https (playing at "ooh look, we are secure" to non tech / clueless web users) .. yet would make lots of calls to http based URIs, rather defeating the point.
Full disclosure: I have had to write js utilizing web sites to pay the bills, not my preference but various functionality demanded / specified by the paying customers (e.g. must use certain js frameworks that their own dev team are familiar with so they can maintain / alter it after handover). So written as someone who can write js heavy web sites, but would prefer not to!