Before the update nothing on my computer had any connection to Amazon as I consider that organisation to be anathema. install the update and suddenly half of my tabs have been redirected. So who do you think was responsible?
Still no news on this? I'd also really like Speed Dial to be actually speedy, without this animation.
Furthermore, as posted somewhere else, it would be great if the zooming of the Speed Dial is not shared with the bookmarks and the history. I always increase the Speed Dial size, but I don't want the other two to be zoomed as well.
@slytheringirl thank you, at least its not just me, what it does its trying to connect, then site can not be reached timed_out on basically everything, then I switch (alt´tab) to another thing I was doing and then it suddenly loaded but if I press reload it is back again to time_out, what could be causing this? oh and Chrome works wonderful for me except I miss the sidebars with messenger and whatsapp
@leocg I do have display settings set to a light gray for the background in Windows 7. But it doesn't look like the page is using that as the background is white. Just like Firefox and Google Chrome. Everything is identical except the log in tables are not there. And I just updated Opera Chrome.
@crisalide said in Has Opera Turbo been killed?:
... Opera Turbo, especially for those who have a consumer connection, was an essential function, one of those that should never be touched, so I don't understand the logic behind this decision.
I'm not an Opera employee, but my best guess is it was a business cost decision, perhaps accelerated by the recent Opera ownership change. Turbo was not a strictly browser-code feature as much as it was a proxy-like filter residing on servers operated by Opera (which compressed the data coming back from a visited website - especially images - thereby reducing the data package size going to the user). So two cost-reduction possibilities present themselves: either it was becoming too expensive to maintain the Turbo browser code in light of the continual chromium engine updates or/and it was becoming too expensive (or bandwidth-competitive) to maintain the proxy-like server network. My personal guess is the latter to be more likely contributor.