![]() Microsoft can't do the same?Īs for someone's comment about anti trust. Nobody should be forced to use any browser that they don't want to but if they are forcing edge for these features then isn't it reasonable to assume that edge has some customization on top of chromium for those features? Chrome has customizations for Google web apps that make them work better and faster. The difference is Windows telemetry is anonymous while chromes isn't. Plus if you're worried about telemetry or analytics then why are you using chrome in the first place? Not only does chrome tell google everything you do in chrome it also gathers more telemetry data on Windows than Windows itself. There's probably a reason they open in edge as well and it's not just because MS wants people to use it. They are both chromium and it's only a couple things that open in edge. ![]() If people are using chrome then I don't understand the problem. They would have no control over that, and that's not a position you want to be in with an OS feature. ![]() Mozilla or Google could make a change that breaks their results pages. They can't do that if it goes to any browser. You can argue that this is not necessary, that any issues that might arise aren't going to be sufficient to justify removing choice, or that the features themselves aren't important enough for it to be worth the lock in, but it makes sense to want to be able to validate certain experiences. It's why it defaults to release which is going to be more stable than dev. They do not want service calls from people who've set a different default browser without actually understanding what that means about why clicking on a widget or running search is resulting in unexpected behaviors, etc. They want to be able to ensure the behavior, end to end, for OS links for non technical people. It can lead to really problematic bugs in the long term.īut they're doing this for a reason that isn't about boosting edge stats too. You don't, as a general engineering rule, want a call that expects something very specific to actually go to something else. Complain that they're using edge links instead of https links as much as you like, because a lot of the behavior you're all complaining about, including the way release edge gets directed to instead of edge dev goes away if they're treated as normal web links. ![]() Redirecting app specific links is a bad thing.
0 Comments
Leave a Reply. |