4 ms·
>They can understand it, but not use it. Right, and isn't that what Google is doing? "Hey, if you send a message in the Java language/API, we will understand
by SilasX 7y ago
>They can understand it, but not use it.
Right, and isn't that what Google is doing?
"Hey, if you send a message in the Java language/API, we will understand it and do the same thing that a real java program will do."
"Hey, if you request that a meal be supersized, we'll understand what you intend and execute the Biggie-size operation, which matches what McDonald's would do."
Of course, there is the difference that, unlike Wendy's, Google is (analogous to) telling everyone "you can ask the cashier to supersize your meal" instead of just rolling their eyes and accommodating confused consumers.
>Going to your fast food example, I'm pretty sure that trademark law applies,
As in the sibling subthread, I think the example sidesteps the trademark complication because Wendy's doesn't ever use "supersize" in promotion, they just passively accept user-initiated requests that use the term, and do so in a way compatible with their McDonald's-derived expectations.
- withjive 7y agoAs an Android developer during the first G1 era, I feel that Google was really taking advantage of the well established Java developer base. Having developers already understand Java, was a huge thing for Android when it first came out. So when you say: > Wendy’s doesn’t ever use “supersize” in their promotions IANAL, So I’m not sure Google didn’t do the same... I also think Oracle is also not happy with that.
- SilasX 7y agoRight but what if the java API is nominally “secondary”: “oh use this Byzantine Android api we have ... but if you just treat it like java, it’ll guess what you mean, ruby-magic-method style”?