3 ms·
This is the thing that really bothers me [from a comment in the post]: > 2) Also realize that the SCOTUS' job is not to decide what's right, but to decide what
by karmakaze 6y ago
This is the thing that really bothers me [from a comment in the post]:
> 2) Also realize that the SCOTUS' job is not to decide what's right, but to decide what's legal given the constraints and allowances of both the Constitution and law. Even if a Justice were to feel like copywriting APIs would have terrible knock-on effects, she would be compelled to rule in favor of granting them if she believed that the laws passed by Congress required it.
So much of the arguments were specific to the Google/Oracle incident and not as much about the implications except for the thing about QWERTY and perhaps some vague analogies. I thought at the SC level it should always consider 'terrible knock-on effects' and act accordingly considering but not strictly bound to what came before.
- ghaff 6y agoWell, they sort of do. When existing precedent is clearly outside the bounds of what's considered "just" today, it's not unknown for SCOTUS to discover a new right or reinterpret a precedent. That said, they (rightly) mostly rely on precedent and the law rather than deciding on the basis of the good of the many by their lights. As someone else in the comments said, I'm on Google's side here on the basis of this being the general industry assumption for a long time and interoperability generally being a good thing. On the other hand, does anyone here honestly believe that a complex API some team spent a lot of time designing isn't really a creative work?