What is going on with these companies?
There must be some business people at Google knowing this, I can't believe they're all patting each other backs saying the new Gmail works better than ever, there must be some folks with some common sense in the upper management.
I have not yet found a computer and browser combination that's capable of handling their site for an extended period. Simply put, if you use it for a long enough time, visit groups you're a member of, scroll through the messages there and talk in group chats the Facebook tab will eventually slow down so much that after a while even your keyboard input will become laggy. Whether that's on a year old 15" MacBook Pro with an i7 and 16 gigs of ram in Safari or a full Windowe 10 desktop with 32 gigs of ram, you'll eventually run into having to close and reopen the tab again.
They just seem to be generating incredibly complex dom trees for the simplest of components for no discernible reason whatsoever. A friend in a similar situation permanently shifted his Facebook usage to exclusively using Messenger.com partly because of this.
You give us zero information, so best we can do is: guess you have the same issues as our own parents and other non-tech lambda people.
https://leantesting.com/write-good-bug-report/
https://www.softwaretestinghelp.com/how-to-write-good-bug-re...
Which brings up the point someone brought up is that the developers, QA testers, and managers at those companies probably have more modern computers and even faster network. But there are some ways around that like VMs and virtual network interfaces that intentionally throttle the speed and performance and I would be surprised (although not TOO surprised) if no one on the QA teams at those companies used them.
Another thing as others pointed out is that these apps are insanely complicated. They have live updating, undo, advertising, inline preview of links, search, autocomplete, etc... tons of features that many users will never use.
And that's just the client-side complexity.
Part of that is due to user demand and part of it is due to the app just slowly getting more complicated over time (call it feature creep and technical debt). And part of that may also be because as one cynical (albeit probably not wrong) person put it, there are huge teams working on many of these features[1] that need to justify their budget by showing "results."
You may also be assuming that 1000 features that are easy to build, maintain, and keep bug free scales to a single system that is easy to do those things. It rarely works that way because components need to interact with each other and by necessity you have multiple people (multiple teams in fact) who need to integrate their stuff together.
[1] Some of the features I'm sure have more team members than my entire startup company just to build one feature.
This link to view GMail as HTML only:
https://mail.google.com/mail/h/
Definitely speeds things along!
Determine if it is external factors (your connection/computer) or the site's fault. Learn something about web dev. in the process.Otherwise I would suggest not to complain on HN but with the supplier that you pay for the quality of this product.
- Autocomplete for most used items ( emails, users, etc. )
- Some real time tagging / categorising feature
- Confirmation blockers on dangerous actions
- Undo button for almost any action
- Fine-grain privacy related functionality
- Text editor with features, which renders whatever you type nicely formatted
- Tons of helpers, video playback functionality, photo gallery, photo uploads, etc.
- All of the above free and because of that, tons of analytics included in the page, which show you a relevant advertisement.
Yeah if you don't like all this you can replace Gmail with Mac's mail app or any other program that sends / reads mails.
You can also replace facebook website with the app on your phone.
But you can't have all those features run fast on slow computers and a slow computer for me these days is something < 16GB RAM or < i7.
Another guess is that the development and testing targets mainly (or only) Google Chrome, which I don’t use. I’m not sure if long running browser sessions (without restarts) cause more issues. But the Facebook pages are heavy, and rendering is a lot slower than it used to be a few years ago.
