Microsoft didn’t control the number one search engine, the number one email client, the number one video site, probably the number one online office suite, the number one smartphone platform…
It was possible to rip people away from Microsoft. That may not be something we can do this time with Chrome.
Try telling someone that moving off of Chrome may mean moving off of every single Google property because Chrome is the only browser they work on by then.
See how easy an argument that is. It’s right up with there with “stop helping capitalism and move to the woods“.
Then it’d be time for round two of antitrust, and I doubt the judge and regulators would feel so understanding about Google keeping Chrome if that is the landscape.
1. The US isn’t doing this. They have a case but aren’t calling for breakup
2. We all know howling anti-trust and appeals take
If Google gets handed the web (let’s say) this year by Apple being forced to allow them, it could be a decade+ before the Google side gets tackled.
And I’m afraid of how much damage they can do in that timeframe.
I think fixing Google’s ownership over Chrome before forcing other browsers on iOS would be less harmless than forcing iOS to allow other browsers than doing Google.
I’m totally good with doing both. I worried about the effects of the order they’re done in.
And I am only saying this about browser engines. This should not be taken to say Apple should be able to do some of the other nonsense they’ve been doing for 10+ years abusing their position.
I think they might be, but only as long as it stays open-source (assuming we mean it works on Chromium and not Chrome). Honestly, I fundamentally don't have a problem with an open-source browser having a monopoly, because the open-source nature means that if things get bad you can always just fork it and make something better.
Yes, it does lead to blocking the traffic but that is the only safe action to do in such an intersection; if an intersection has traffic lights, there's enough traffic that stop&give way is not a viable operation.
Usually in that case you would make it a priority to the right /or left so that everyone only has to look at one side (besides the pedestrians) and in a very busy intersection people with common sense and education naturally do an alternance where you give way to every other car.
I don't know if waymos are programmed for that and it could very well be that there were so many pedestrian crossing it wouldn't apply it anyway.
Author of the project here. This project reuses parts of OpenHands, but the code is written from scratch to make it into native Android application and implement on-device inference.
There's no point doing that given the Responses API has to be ad-free unlike ChatGPT Web API for applications to function correctly (no way baking ads into responses sent to third party services using your language model just as a natural language processor), and you have to keep the Web API tiers that's more expensive than the same amount of tokens of equivalent Responses API use also ad-free becuase otherwise the "wrong way of payment" paradox would arise.
reply