The item 3 is very impressive. Anyone knows if the other major browsers test for such thing?
Building a more power-efficient browser
51–60 of 105 posts
Re: Building a more power-efficient browser
#52re: The reading mode button animation batery use improved Who needs the button animation at all? I like them not moving, every movement of something that's always on the same place is distracting. It's stunning on what they spend the energy of the management and the programmers, not only of the CPU's and GPU's of all of us. "We replaced the traditional XAML animation with a timed GPU transform, and now animate the co…
It's a hint to users that reading mode may provide a better experience. When we introduced it, reading mode usage went up; without the (very subtle) animation, users weren't aware when the feature would be useful.
And if I'm not wrong, Safari was the first to have it, years ago, at the time Jobs was there. Never animated.
Anyway, if the feature is useful, people will use it. If it's not, they won't. Not making the whole experience a "big ad" is an example of a taste. Microsoft managers however really like everything moving like in ads including the tiles in the "start" menu. Luckily they at least can be "unanimated," I hope that feature remains (but unluckily I believe I have to do it one by one).
Re: Building a more power-efficient browser
#53Another great way to save a ton of energy and bandwidth is to block ads. Glad to see that they are finally allowing ads. Been long enough. Still a mediocre browser though IMO. iamleppert nailed it on the head.
Do you mean that they are finally allowing ad blockers, via the extension support coming this summer?
Re: Building a more power-efficient browser
#54Earlier quoted context omitted.
> you could run Windows in BootCamp but it isn't tuned for that and is actually hampered How is bootcamp'ed windows hampered? It works perfectly fine for me. In fact, it's better than many Windows laptops I've used because they almost all ship with so much bloatware on them.
The HW has proprietary power management features that Windows cannot take advantage of. For the end user it's probably no big deal, but I think the commenter you replied to is right - power management is a delicate dance between hardware and software, and not all hardware is accessible from all software on every platform.
Re: Building a more power-efficient browser
#55re: The reading mode button animation batery use improved Who needs the button animation at all? I like them not moving, every movement of something that's always on the same place is distracting. It's stunning on what they spend the energy of the management and the programmers, not only of the CPU's and GPU's of all of us. "We replaced the traditional XAML animation with a timed GPU transform, and now animate the co…
It's a hint to users that reading mode may provide a better experience. When we introduced it, reading mode usage went up; without the (very subtle) animation, users weren't aware when the feature would be useful.
Re: Building a more power-efficient browser
#56Some interesting optimizations in here, but I'm curious about this one in particular: > With the Anniversary Update, Microsoft Edge only executes background JavaScript timers once per second in background tabs. More importantly, these timers are coalesced with other work happening across Windows. Microsoft Edge doesn’t wake up the hardware to perform work. Instead we tag along with other work happening across the sys…
Re: Building a more power-efficient browser
#57Re: Building a more power-efficient browser
#58Some interesting optimizations in here, but I'm curious about this one in particular: > With the Anniversary Update, Microsoft Edge only executes background JavaScript timers once per second in background tabs. More importantly, these timers are coalesced with other work happening across Windows. Microsoft Edge doesn’t wake up the hardware to perform work. Instead we tag along with other work happening across the sys…
I'm not sure about Edge in particular, but on most platform runtimes "timers" are separate from IO-availability-triggered asynchronous events. When a WebRTC data connection signals its send channel has become unblocked/receive channel has data available, a handler will be called right then; there's no timer involved. Timers are just for things that have no relevant IO to control them, like animations.
[0] https://winblogs.azureedge.net/win/2016/06/cpu-utilization-1...
Re: Building a more power-efficient browser
#59Earlier quoted context omitted.
The HW has proprietary power management features that Windows cannot take advantage of. For the end user it's probably no big deal, but I think the commenter you replied to is right - power management is a delicate dance between hardware and software, and not all hardware is accessible from all software on every platform.
This statement is true for any laptop running Windows, it is not MacBook specific
Apple does not. Base line Windows power management (generic Intel drivers, etc) is probably good enough for them.
Re: Building a more power-efficient browser
#60Earlier quoted context omitted.
It's a hint to users that reading mode may provide a better experience. When we introduced it, reading mode usage went up; without the (very subtle) animation, users weren't aware when the feature would be useful.
Still it shows what's done just to make somebody's bonus (or just prestige in the meetings?) thanks to the change in the telemetry reports. Luckily both Safari and Firefox don't animate it. And if I'm not wrong, Safari was the first to have it, years ago, at the time Jobs was there. Never animated. Anyway, if the feature is useful, people will use it. If it's not, they won't. Not making the whole experience a "big ad…
They tend to love it after I pointed out to them. Microsoft is probably doing the right thing here.