6 ms·
Any reason you're not supporting the iPhone 5 or 5C? Is there something you need which they don't support?
by edd 11y ago
Any reason you're not supporting the iPhone 5 or 5C? Is there something you need which they don't support?
- RKearney 11y agoThe 5 and 5C do not have 64 bit processors, which is a requirement for Content Blockers.
- angersock 11y agoApparently blocking ads is harder than landing on the Moon. :|
- zem 11y agothe moon isn't actively altering its surface and orbital pattern to prevent you from landing there
- pc86 11y agoMaybe it is and that's why they faked it! /s
- golergka 11y agoSaturn V rocket is not yet required for content blockers.
- 0xdeadbeefbabe 11y agoModern designer and UI experts demand better--really worse--UI than the moon lander had[0]. This can make almost any project harder than landing on the moon. [0] https://www.youtube.com/watch?v=Qj2IETkScWA https://www.youtube.com/watch?v=Qj2IETkScWA
- uremog 11y agoThe moon doesn't generate as much money as ads.
- 0x38B 11y agoContent blockers seem to work on 32-bit devices if you compile for them: "Yes, but I'd guess it's an arbitrary limitation—at least it seems to be for A6 devices. BlockParty works perfectly on my iPhone 5C and apparently on @wadetregaskis' iPhone 5, both of which are 32 bit A6 (and not officially supported). I get all the relevant menus, and it does block ads (even the huge easylist conversion works, albeit poorly)." [1] 1: https://github.com/krishkumar/BlockParty/issues/9#issuecomment-141373576 https://github.com/krishkumar/BlockParty/issues/9#issuecomme...
- MBCook 11y agoApple chose not support 32 bit devices in their blocking API, which isn't too unreasonable. I imagine it kept the code quite a bit cleaner (or avoided having to run parallel implementations to get good speed).
- comex 11y agoAs the parent says, the API works fine as is, today, on 32-bit devices - you're just not allowed to submit code to the App Store that takes advantage of this. There is no JIT or anything else inherently architecture specific in the WebKit content blocker implementation. Thus the restriction comes either from a semi-arbitrary determination of the speed of Apple's first 64-bit processor, and/or the amount of RAM that came with it, as the boundary below which content blockers might cause unacceptable performance regression (despite their /improving/ performance on many sites)... or from some odd marketing plan to sell newer devices. Hard to say which.
- TazeTSchnitzel 11y agoPersonally, I doubt it's a marketing thing. Apple do sometimes restrict software features to specific devices (Siri when it launched originally), but this is rather oddly processor-dependant. So I assume it's a performance thing.
- stephenr 11y agoiOS content blockers don't support 32bit CPUs, apparently for performance reasons. This is an Apple decision, not a Mozilla decision (all other iOS content blockers face the same limitation)
- lkiernan 11y agoBecause Apple want you to upgrade plzkthx
- shortstuffsushi 11y agoNot sure why you're being downvoted. I actually had the same question, and found out by seeing the responses to your question that 64 bit is required.