Live data from Hacker News

Apple ResearchKit on GitHub

researchkit.github.io

41–50 of 113 posts

Re: Apple ResearchKit on GitHub

#41
post #20
post #7

Earlier quoted context omitted.

Java, is it the thing they used to sue on API copyright? Good demonstration of how to mess with "open-source" IMO. If you remove what they got from Sun, what reminds?

Sun would have sued Google if they had the money for the lawyers[0]. Initially I was partnering with Google, but now I side with Oracle's decision, as it is now proven how Google just pulled a Microsoft and fragmented the Java eco-system. Now we are stuck with partial Java 7 assuming 4.4 devices, good luck using try-with resources in lower versions and no plan for future versions as of the Android Developers Fireside…

Actually another post on Sun wouldn't have sued. Sun's CEO Jonathan Schwartz testified on behave of Google. He even blogged a congratulations to Google for releasing Android running Java. http://web.archive.org/web/20101023072550/http://blogs.sun.c...

http://www.theverge.com/2012/4/26/2977858/former-sun-ceo-jon...

Re: Apple ResearchKit on GitHub

#42
post #40
post #6

Earlier quoted context omitted.

I can sense some Strong Anti-Oracle Bias here. Oracle is one of the major contributor to open source, see the lineup here, chances are you're using some of them: https://oss.oracle.com/ starts with Java

> Sense some Strong Anti-Oracle Bias here Use to be a System Librarian and had to run Oracle DB. Issues: 1. OpenOffice gave it to Apache Foundation and not LibreOffice 2. MySQL is abandoned by many major users but we have MariaDB 3. Java suite against Google to make API Copyright-able 4. Oracle's White Paper stating that Open Source cost more and is less reliable. 5. Oracle Linux (Just a rip off of Red Hat) 6. KSplic…

Just to clarify, legacy Ksplice customers are still supported under their original contracts, Ksplice is available to new customers with Oracle Premier Support, and finally, Ksplice updates are still being provided for free for all current Ubuntu and Fedora distros.

Disclaimer: I'm on the Ksplice team.

Re: Apple ResearchKit on GitHub

#44
post #3

Is there anything about App Store guidelines? Curious if Apple is going to require any kind of IRB approval first.

The other big issue I see is: if you try to do any kind of population or cohort study with this, how on earth do you correct for the bias that comes from only sampling iPhone users? It's borderline facetious to claim that there is no sampling bias, and it will be a nightmare to control for.

Re: Apple ResearchKit on GitHub

#46
post #41
post #20

Earlier quoted context omitted.

Sun would have sued Google if they had the money for the lawyers[0]. Initially I was partnering with Google, but now I side with Oracle's decision, as it is now proven how Google just pulled a Microsoft and fragmented the Java eco-system. Now we are stuck with partial Java 7 assuming 4.4 devices, good luck using try-with resources in lower versions and no plan for future versions as of the Android Developers Fireside…

Actually another post on Sun wouldn't have sued. Sun's CEO Jonathan Schwartz testified on behave of Google. He even blogged a congratulations to Google for releasing Android running Java. http://web.archive.org/web/20101023072550/http://blogs.sun.c... http://www.theverge.com/2012/4/26/2977858/former-sun-ceo-jon...

If you have bothered to read what Gosling had to say about it:

"Google totally slimed Sun. We were all really disturbed, even Jonathan: he just decided to put on a happy face and tried to turn lemons into lemonade, which annoyed a lot of folks at Sun."

Re: Apple ResearchKit on GitHub

#47
post #7
post #6

Earlier quoted context omitted.

I can sense some Strong Anti-Oracle Bias here. Oracle is one of the major contributor to open source, see the lineup here, chances are you're using some of them: https://oss.oracle.com/ starts with Java

Java, is it the thing they used to sue on API copyright? Good demonstration of how to mess with "open-source" IMO. If you remove what they got from Sun, what reminds?

Open source doesn't mean you get to ignore the license.

Re: Apple ResearchKit on GitHub

#48
post #39

Earlier quoted context omitted.

"This line was probably required to get some manager at Apple to sign off on this." I agree here :) "Apple logo or the word 'iPhone' didn't cause irreparable damage to their trademark." As I said, this is a problem either no company who uses the BSD license has or all of them have it. "But I'd rather have a company add _one line_ to an already minimal license than not open source at all out of this fear." I don't agr…

It's probably a problem all of them have. Apple is just the only company that cares enough to make a big deal about it in advance, rather than imagining that they'll just let things slide for now and argue post-facto in some later court case that the license should be read as not granting trademarks. In other words, this isn't like the nuclear reactors bit—this is something that could actually belong in the BSD licen…

1. I strongly disagree with the idea that they are the only ones who would consider it a large deal enough to do something if it was a real fear. It's somewhat ridiculous to believe that, say, Google or Facebook, wouldn't do the same if they thought it was a concern.

2. The part about "having to argue post-facto" would be a valid line of argument if, as i pointed out, there wasn't already plenty of precedent that shows their fear is completely and utterly unwarranted.

In fact, i doubt they could even cite a single time a judge even considered this a non-crazy argument.

In other words, this in fact, is exactly like the nuclear reactors bit. It doesn't actually belong in the license, because if was a real concern:

A. There would be at least some case somewhere that concerneed folks.

B. After 20+ years of BSD licenses, it'd already be there

Re: Apple ResearchKit on GitHub

#50
post #3

Is there anything about App Store guidelines? Curious if Apple is going to require any kind of IRB approval first.

The other big issue I see is: if you try to do any kind of population or cohort study with this, how on earth do you correct for the bias that comes from only sampling iPhone users? It's borderline facetious to claim that there is no sampling bias, and it will be a nightmare to control for.

My guess is that some of this will make field collection with iOS devices easier, rather than relying on the user's device.
Post reply on HN