141–150 of 403 posts
Earlier quoted context omitted.
Oh, it's awful, I agree. This is the nicest layout but the JS is terrible. I've reverted to a plain-HTML layout.
To whoever downvoted this: I am the author of the post above, and in response I've removed the JS-centric layout.
Oh god, please change the title. It's about timers, not bandwidth. I was already imagining streaming music from Spotify and having hiccups all day.
It's awesome to see Chrome trying to improve performance for people with many tabs open, which is many of us. I use a LOT of tabs, and the best plugin has been The Great Suspender. Highly recommend it for anyone who wants memory & CPU back and keeps many tabs/windows open at once: https://chrome.google.com/webstore/detail/the-great-suspende...
same here using The great suspender, how does this throttle thing relate to the suspender?
Earlier quoted context omitted.
I meet many tab hoarders (always open a new one, never close any, ending up with hundrets), but just can't wrap my head around it! I hate having more than 6-7 simultaneously open because it gets increasingly harder to keep an overview of what you're doing. The same applies for IDE tabs or windows. Too much of them and finding the right one becomes increasingly hard, and losing the thread more likely.
Not if you use Tree Style Tabs. I've been using it for years and I have no idea how other people can efficiently browse the web without it.
Earlier quoted context omitted.
Problem is, there is no server. All client side. So the tab on which you click "run simulation" is effectively the "server", except it stops running when the user switches tabs.
The fact that you don't have a backend is the limiting factor here.
It's awesome to see Chrome trying to improve performance for people with many tabs open, which is many of us. I use a LOT of tabs, and the best plugin has been The Great Suspender. Highly recommend it for anyone who wants memory & CPU back and keeps many tabs/windows open at once: https://chrome.google.com/webstore/detail/the-great-suspende...
I meet many tab hoarders (always open a new one, never close any, ending up with hundrets), but just can't wrap my head around it! I hate having more than 6-7 simultaneously open because it gets increasingly harder to keep an overview of what you're doing. The same applies for IDE tabs or windows. Too much of them and finding the right one becomes increasingly hard, and losing the thread more likely.
On the other hand I rather use native apps, when given the option.
Which I also only keep the ones for the task at hand open.
Earlier quoted context omitted.
Pinned tabs would be an easy solution for this. "Don't throttle pinned tabs"
While this is elegant, its still dangerous. There are online payments that could check whether your booking is complete in the background by periodically firing ajax calls, bulk updates or uploads, etc.
Earlier quoted context omitted.
Pinned tabs would be an easy solution for this. "Don't throttle pinned tabs"
A common use-case is tabs that are streaming music. I'm not sure if most users are even aware of pinned tabs.
I have an option set in FF's about:config that disables loading of my pinned tabs on startup, so I regularly keep 200-300 tabs open and only activate the ones I need.
Sometimes it takes weeks to clear my tabs because I barely see a performance hit from having so many open.
Earlier quoted context omitted.
Problem is, there is no server. All client side. So the tab on which you click "run simulation" is effectively the "server", except it stops running when the user switches tabs.
The fact that you don't have a backend is the limiting factor here.
Earlier quoted context omitted.
There's no right way to do it. What's hard is understanding which question you want to ask in any given situation. I don't see the issue. You admit that answering all of these questions is easy. The hard part is lawyering which question to ask. This is not a data reporting problem. This is a data interpretation problem. A good reporting tool should not be interpreting (or forcing an opinion) on the end user. You beli…
"This is a data interpretation problem." That's what I said. "Defining it is what's hard." You seem to understand what I'm saying, and agree with me, but insist on arguing for some reason I cannot comprehend.
You seem to understand what I'm saying
and agree with me
Measuring memory usage is hard on a modern OS.
Defining it is what's hard
I stated measuring is literally the simplest thing. You said ah but what you measuring. That isn't dependent on the tools, or OS. So why did you state it was?