Also, one thing I noticed about most web “upgrades” is that they now require javascript be turned on to do anything. That’s sheer laziness on the part of the “developers”, and it makes the whole experience a dog. Instead of a page loading quickly, it takes forever while everything slow-loads in bits’n’pieces, it’s blocky, unresponsive, filled with lag, you have no idea if the page is hung while it’s waiting for the retarded little facebook/pinterest/twitter/other logos to load in a retarded in-the-way sidebar, and everything just turns to $#|+.
GB? Broken. AX? Broken. UPS? Broken (whoever designed/included that “assistant” popup should die a horrible fiery death). Even trade-rags have such a huge difference with js turned on vs off. Off, you get a nice clean article, ’though now usually without any inline images loaded. On, and you get hideous background images, popups, sidebars, all sorts of pure CRAP that pollute the page and make it impossible to just read the damned thing in peace.
Plus, with all the bloat (both source and cpu cycles), it becomes just painful to try to load a page on older equipment. When you hear the fan revving fullspeed all of a sudden, everything else locks up, then get a “This script is unresponsive… end it / wait for it / what?” popup, oh, that’s so much fun.
Sites that require js to do anything, I’ve largely abandoned, and use only if I have to, and then, only on certain machines that don’t croke when you try. Any phones, etc., that use browsers like Midori (zero js support) are effectively locked out from those sites. No great loss, usually, but sometimes, on rare occasion, you’d actually want to suffer through it just to see something. but can’t.
All that said, if “upgraded” forum sw were to require js just for basic functionality, I know I’d be gone (except maybe in readonly mode), but dunno how many others would, whether by choice or necessity.