Comment Re: For some value of "bug" (Score 1) 272
No preview on mobile.
No preview on mobile.
And then there's "it's 2017 and we've never heard of UTF-8" bugs.
Thereâ(TM)s âoeyou forgot to check array bounds hereâ bugs, and then thereâ(TM)s âoeyour entire design is fundamentally fucked and insecureâ bugsâ¦
It is very rare for a company designing a new product to search the patent database for ideas to license, and equally rare for inventors to go out and market their inventions to established companies.
That's partly because if you did search for it, the other side can claim you found their patents, and thus your infringement was now "willful", which results in triple damages. Since you'll be sued either way, it's safer to go in blind. Tech companies specifically instruct their employees not to search for patents for this reason.
There's enough coal in the USA to power the country for a century.
And there's enough wind in the USA to power the country forever.
Paypal's logo looks like the butt of someone wearing blue jeans. Pandora's does not.
I assume the ultimate motivation for this project was as a backup plan in case of a disastrously adverse ruling in Oracle v. Google that would have led to Google deciding to excise any connection between Android and Java. It's probably since taken on a life of its own, as these things tend to do. (Also, I wonder if the names Fuchsia & Magenta are references to the ill-fated Pink OS that started life as a ground-up Mac OS rewrite at Apple and morphed into the Taligent corporation?)
Additionally, if your system deals with dates or human names, whatever limitations you think are reasonable are, in fact, wrong.
In fact, I am not sure why go to such great lengths to obtain UDID when device MAC address is readily available (and must be for variety of software to work) and globally unique.
MAC Address is no longer available since iOS 7. You can request it, but you'll get the same fake value of 02:00:00:00:00:00 on every iPhone. UDID is not available, either.
There's IDFV, the Identifier For Vendors, which is different for each vendor on the phone, and gets reset if you remove all the apps from that vendor on the phone. (That is, two apps from Google will see the same IDFV, but a different one from the one Facebook sees.)
Then there's IDFA, the Identifier for Advertisers, which the user can reset at any time via system settings, and which Apple will reject your app for if they catch you using it for anything other than ad-tracking.
The end result is that there is no longer any stable cross-app identifier that survives app uninstalls and user attempts to avoid tracking, by explicit design.
Whether this can be turned into a viable business model is of course a separate question, but acting like Google is blameless by just TAKING that data and reusing it without permission is -- well, Google is certainly morally suspect at a minimum here. If businesses like this can't make money gathering such data, who will gather the data?
That's easy, Google. They already take the perspective that if you perform a search and the answer isn't available online, it's Google's problem and not the user's, so they've put substantial effort into collecting and curating data about things into their Knowledge Graph so they can present answers directly to the user.
The problem line is [oneish integerValue], which returns zero, and the rest of your code is just trying to obfuscate this. This is because NSDecimalNumber doesn't overrider integerValue, so it returns the inherited implementation, which returns zero. This is unexpected, but not undocumented. See the Subclassing Notes at:
https://developer.apple.com/re...
I'll note that in Swift, integerValue no longer exists, having been folded into intValue, which gives the expected result of one (just like intValue in Objective-C).
It's right there in the title—they have an electric CEO!
In this case, it was a picture sent (most likely) with the intent to injure or induce a seizure. There's a difference between offensive and injurious intent.
Intent seems pretty easy to establish here, seeing as how the message accompanying the picture was “You deserve a seizure for your post.”
Except, you see, that humans are in portrait orientation most of the time (as the name suggests, you see), and we're the majority of subjects of mobile video. And, since so many people are watching video on phones, it turns out that the majority of screens are also in portrait orientation most of the time. So, really, the problem is crummy playback systems that fail to present vertical videos at the maximum possible size.
Updates for iPhones come direct from Apple. There's no gating by carrier, because Apple had the clout to tell the carriers to shove it when it came to customizing it with their particular crapware.
It is easier to write an incorrect program than understand a correct one.
