4 ms·
Are you genuinely confused that Apple didn’t prioritize support on Android and on #3 (4?) browser? Or are you just disappointed, but expressing it as bewildern
by khazhoux 2y ago
Are you genuinely confused that Apple didn’t prioritize support on Android and on #3 (4?) browser? Or are you just disappointed, but expressing it as bewildernent?
- michaelmrose 2y agoCompetent web development has usually been associated with standards compliant sites that work everywhere. In 2024 its weird that someone who isn't a moron manages to break the web. One would assume this is deliberate to retain some competitive edge. If so why bother a map product that doesn't work where I need it 99% of the time is completely useless. They might as well have retained more advantage yet by making it mac safari only.
- scarface_74 2y agoYes because I’m sure that Apple is really worried about competition from Firefox. No serious web developer thinks that you don’t have to test and special case for different browsers. It also blocks Apple’s own unsupported browsers
- michaelmrose 2y agoCompetition from Android adding value to the Android platform is not ideal.
- scarface_74 2y agoIs realistic to think that Apple executives are concerned with iOS users switching to Android because Apple Maps is available on the web?
- echoangle 2y ago“Not prioritizing support” is a nice euphemism for explicitly blocking it. They could have just left it alone or added a dismissible banner saying “this browser isn’t supported, don’t report any bugs you find, we don’t care”, but they went out of their way to prevent you from accessing it.
- bastawhiz 2y agoI'm saying that in the year of our lord 2024 (with arguably the best browser compatibility we've ever had) they managed to—against all odds—build a website which doesn't work on the most popular mobile operating system in the world and the second most popular rendering engine in the world.