If this is not working out for Google, perhaps it's because the business is fundamentally incompatible? But I have problems believing that. The outcome would be too good :-)
5,403 karma · joined August 2, 2011
If this is not working out for Google, perhaps it's because the business is fundamentally incompatible? But I have problems believing that. The outcome would be too good :-)
OK, sure it's nice that right now every site or company I ever had any interaction with no longer feels like they can keep my email on file to continuously spam me.
But this state won't last right? I assume that everything I sign up for in the future will have a load of legalese to circumvent this as much as possible?
I'm sure there's a Bugzilla bug about the "X11; Linux x86_64" in the headers, and I'd be terrified to open it.
By displaying deceptive ads about competitors in their flagship product?
Get out.
Mostly slow because they need to display a lot of...Google Ads?
Typically standard bodies avoid this by requiring two independent implementations, but the market situation really means that the standard is what Chrome implements, and nothing else.
I think this is what tripped me up before. I closed my business years ago but it was completely impossible to get Google to fix this. Now it fixed it "by itself".
Just a warning to everyone before signing up with your main Google account :-)
Well, yes and no. The whole problem with WebSQL was that it effectively meant using SQLite and never anything else that wasn't completely bug compatible.
So the whole problem with WebSQL was that it was, de facto, a web standard built around giving an SQLite interface client-side.
So good that they got rid of it in their new chips.
I think Qt wins in all other domains though. Documentation, extensiveness and quality of the non-GUI stuff, etc.
But not having native widgets kinda sucks. You can see that when you make that compromise, the question comes why not to use Electron (which is a competitor of those two in reality).
Does it even qualify as a tech demo if the result only exists in DeepMind's lab?
You can't disconnect the search part from the discussion, as the search selectivity is ALSO learned by the neural network.
(cough Netscape cough)
I already did. Much of the stuff you mentioned has always been enabled and had nothing to do with telemetry. This is most obvious with the update checks. And yes, you DO need to send information to know which add-ons to update. Probing every installed add-on to see if there's an update amounts to sending over the list of installed add-ons. Let's be forthright about that.
I quoted an article from one of the Telemetry engineers explaining that now LESS data is collected by default.
I think that's a good enough rebuttal to your claim that there has been a change of direction to collect more.
I have no idea where you pull the "this seems to include what URL's you're browsing; this could be a security risk for apps like Dropbox and OneDrive" stuff from. The only place I know of that these could potentially be recorded is a crash report, and this has always been the case if you allow it to send crash reports back because they contain the stack contents.
A public discussion was started to get to know how people felt about privacy conserving telemetry collection that would be opt out by default. There was massive negative feedback (duh). The feature did not ship in 57.
https://medium.com/georg-fritzsche/data-preference-changes-i...
"instead we always collect LESS data on Firefox release."
Firefox has been shipping with a sandbox for a while, let alone e10s. Is that an old post?
That's totally an option for our product, great idea! Why did I never think of this!
No seriously we are shipping, using OpenCL and it gives about a 20 times performance advantage for most users regardless if they have AMD or NVIDIA hardware. If something that's actually better than OpenCL comes along (or if AMD RTG goes out of business) I'll switch to it no heart broken.
But that hasn't happened yet.