The beauty of lightweight HTML is that loading the next page feels responsive, without any frameworks, callbacks and content updates. Wish we hadn't forgotten that.
I recently tested it, and even on a desktop browser "new" Reddit loads slower than old.reddit.com when e.g. navigating from the thread list into an individual thread – the initial page load isn't substantially faster with new Reddit, even though the server has to serve less dynamic content, and then you always spend another second or two waiting for the comments to actually load.
Whereas with old.reddit.com the initial page load might possibly be minimally slower, but end-to-end it's still noticeably faster, because everything, including the comments, loads in one go.
On an underpowered phone with mediocre JavaScript-performance it's even worse, so old.reddit.com is even more preferable (besides the fact that you're also getting around all the "are you sure you don't want to rather view this in the app" nonsense that way), even though it means having to rely on the browser's font inflation-algorithm for getting readable text instead of having a layout that's natively written to accommodate small screen sizes.
The internet has become rife with horrible redesigns that companies are holding back for years on end on forcing all of their users to move to, because on some level they must finally realize that the redesigns are regressions. There aren't even any big fashionable trends right now (like "flat") that can be used to dress up the redesigns as a "modernization" or an "update," because the new versions don't look any newer.
It's a good sign. Maybe unnecessary redesigns that remove functionality and lower information density are reaching a Perl 6 moment. Instead of force migration and destroying your product, the new designs have to compete with the old ones. If it's upsetting that this means that you're maintaining two websites at once, then ditch the new design entirely and just fix the old design (that made you successful.)
The new designs are often a result of the fact that managers can get credit for overseeing something new that becomes successful, but not for maintaining something old. So companies continually churn out useless new versions of things because of bad incentives. I've heard that Google is particularly prone to this, but I can't find the references for it.
This sort of thing also leads to TV shows with short lifespans.
(If it's a product that can be developed by one person, programmers may be involved instead of managers, but not much is like this any more.)
The title is clickbaity, as far as I can see you still can disable chat and meet in order to get rid of the left bar, which is pretty close to the old design, it makes sense that they don't want to maintain both versions and it doesn't seem like a plot to ram chat down your throat.
11 comments
[ 3.1 ms ] story [ 39.3 ms ] thread[1]: https://mail.google.com/mail/u/0/h/1pq68r75kzvdr/?v%3Dlui
Whereas with old.reddit.com the initial page load might possibly be minimally slower, but end-to-end it's still noticeably faster, because everything, including the comments, loads in one go.
On an underpowered phone with mediocre JavaScript-performance it's even worse, so old.reddit.com is even more preferable (besides the fact that you're also getting around all the "are you sure you don't want to rather view this in the app" nonsense that way), even though it means having to rely on the browser's font inflation-algorithm for getting readable text instead of having a layout that's natively written to accommodate small screen sizes.
It's a good sign. Maybe unnecessary redesigns that remove functionality and lower information density are reaching a Perl 6 moment. Instead of force migration and destroying your product, the new designs have to compete with the old ones. If it's upsetting that this means that you're maintaining two websites at once, then ditch the new design entirely and just fix the old design (that made you successful.)
This sort of thing also leads to TV shows with short lifespans.
(If it's a product that can be developed by one person, programmers may be involved instead of managers, but not much is like this any more.)