On a site with lots of ads (including a popup ad), social media "sharing links", a sidebar with unrelated content, and persistent top- and bottom bars.
57 karma · joined October 14, 2010
On a site with lots of ads (including a popup ad), social media "sharing links", a sidebar with unrelated content, and persistent top- and bottom bars.
help <command>Now it finally gets more interesting!!! Bit hacks #1 - #5 were kind of boring to be honest.
Does anybody know a practical use case for that? I have personally never encountered a situation were I needed to manipulate the right most 1-bit.
Otherwise it's a nice introduction to bit hacking.
Alternatively, they could team up with the other manufacturers and boycott carriers which refuse to sell their phones as-is. But they simply don't seem to care about their end-users as much as the carriers (and neither does Google apparently).
edit: spelling.
You missed my point, which was that the crippling is not Android's fault but that of the carriers and phone manufacturers. Its also not due to some inherent property of iOS that it doesn't have any crapware, but thanks to Apple caring about their customers more than about the carriers.
To Apple, carriers are not customers. They're generally hindrances and they might be partners, but Apple's customers are end-user.
Not so for HTC or moto.
Exactly. But again, this has nothing to do with Android or its openness.
Apple is the only manufacturer that was able to convince carriers to sell their phones without any of that garbage. I don't know what is stopping HTC/Motorala/Samsung from trying to enforce similar conditions for its Android-based devices. I guess the carriers simply have too much control over what gets into the market and refuse to sell anything that they aren't allowed to tamper with.
However, I agree with you that the Android brand will suffer very badly from this.
Since Android is Apache-licensed, the openness isn't enforced to all users of the software.
However, if printk would be declared with __attribute__((format(printf, 1, 2)) (I don't know if it is), gcc would warn if the format string contains specifiers which do not match the given types, regardless of any typedefs.