News for hackers. Stuff that matters.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DevX101 on Saturday November 08, 2014 @10:21AM (#8577076)
Although these issues are very important, something feels wrong about having the Supreme Court justices (avg. age ~70) rule on tech matters like this.

We need a new legal system for arbitrating disputes in technical disciplines overseen by a panel of technical experts. Or perhaps a trial by jury where the selection criteria is employment in the relevant discipline for at least 10 years (academia or corporate).

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by dragonwriter on Saturday November 08, 2014 @11:19AM (#8577276)
> Although these issues are very important, something feels wrong about having the Supreme Court justices (avg. age ~70) rule on tech matters like this.

Its not a tech matter, its a matter of the application of Copyright law. Its exactly what the Supreme Court exists to do.

> We need a new legal system for arbitrating disputes in technical disciplines overseen by a panel of technical experts.

Specialized trial or intermediate appellate courts of this type may make some sense (though such a specialized body --whose members are no doubt both drawn from and likely to leave to industry -- runs a particular risk of regulatory capture and becoming a body that reflects very well the interests of the bigger players in the industry), but I don't see any good reason for fragmentation at the top of the judicial branch just because technology, so I don't see any reason that ultimately such issues wouldn't end up with the Supreme Court.

> Or perhaps a trial by jury where the selection criteria is employment in the relevant discipline for at least 10 years (academia or corporate).

Specialized juries defeat the purpose of trial by jury -- and, anyway, then you just create a bunch of additional litigation over the boundaries of the "relevant discipline" for each case as each side tries to set the experience qualifications to suit the pool of jurors it thinks will be most favorable.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by wyager on Saturday November 08, 2014 @10:33AM (#8577124)
>Or perhaps a trial by jury where the selection criteria is employment in the relevant discipline for at least 10 years (academia or corporate).

This could be egregiously abused without too much cleverness.

"Oh, you're self employed in software? No jury duty for you." "Oh, you don't work for GE, the only company approved by the 'What Counts As Corporate Software' board? No jury duty for you."

One must be very careful advocating for the creation of special courts. History is rife with examples of these being particularly corrupt and deplorable.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DevX101 on Saturday November 08, 2014 @10:37AM (#8577135)
You might be right. But our current system is already egregiously abused with minimal cleverness.

One can predict with high accuracy a SC Justice's vote on most cases based on the political party of the president who appointed him/her.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by dragonwriter on Saturday November 08, 2014 @11:25AM (#8577295)
> One can predict with high accuracy a SC Justice's vote on most cases based on the political party of the president who appointed him/her.

Having taken a number of law and judicial politics courses, I can say this has been studied and its not at all true. You can tell with some accuracy a SC Justice's vote on issues that had high political salience at the time the individual justice was appointed by the position of the appointing administration on those issues, but predicting votes by party identification fails rather drastically for most other issues. There's a few evergreen issues that have had both high political salience and fairly consistent partisan breakdown of positions over a long time (e.g., abortion, gun control), and so these issues tend to be pretty consistently predictable by party ID.

OTOH, most issues aren't like that (though issues that get lots of mainstream news coverage are disproportionately likely to be -- though even there many aren't), and issues like the particular one here (whether APIs are within the scope of copyright) haven't ever had high political salience.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by danielweber on Saturday November 08, 2014 @05:17PM (#8578314)
Yeah, that comment was silly. SCOTUS decides ~100 cases a year, and less than 10 are 5-4 decisions. Even even some of the 5-4 votes aren't split along ideological lines.

Sometimes you can predict how a given Justice will act, based on how he feels about the specifics of similar cases.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rpedela on Saturday November 08, 2014 @11:04AM (#8577233)
Overall it seems to self-correct which sometimes takes decades. While flawed, it is pretty good.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by indymike on Saturday November 08, 2014 @11:44AM (#8577377)
The entire US system is predicated on regular citizens making the most important decisions to protect against unjust and corrupt decisions made by experts (judges). You example is EXACTLY the problem with the idea of special courts or special juries.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by kybernetyk on Saturday November 08, 2014 @11:15AM (#8577266)
> avg. age ~70

Why is that a problem? It's certainly possible that the judge was an avid home computer enthusiast in the 1980s and knows about tech.

Old age doesn't automatically mean technological incompetence anymore.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by woofyman on Saturday November 08, 2014 @11:21AM (#8577281)
Nor does youth guarantee technical competence. As a 55 year old developer, I'm particularly sensitive to this kind of blatant ageism.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by shangxiao on Saturday November 08, 2014 @11:36AM (#8577337)
I thought developers over the age of 35 were taken out the back and shot, how did you escape??

Just curious as I turn 35 in a couple of years...

Edit: to the person who downvoted this, it's a joke in case you didn't notice

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by woofyman on Saturday November 08, 2014 @11:49AM (#8577388)
Good question. Luck and hard work mostly.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by orangecat on Saturday November 08, 2014 @10:23PM (#8578992)
Old age doesn't automatically mean technological incompetence anymore.

For example, Judge Alsup was born in 1945 and demonstrated a perfect understanding of the issues in his ruling. As I recall he even taught himself Java programming during the trial.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by pdabbadabba on Saturday November 08, 2014 @11:19AM (#8577275)
Yes, and remember that each justice has an office full of clerks who will typically be in their late 20s and early 30s advising them.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by stonogo on Saturday November 08, 2014 @11:25AM (#8577296)
The problem is the reprehensible ageism inherent in claiming older people are not capable of understanding technology. The same ageism you are implicitly supporting by "reassuring" us that young people (hence, magically tech-savvy people) will have input.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by pdabbadabba on Saturday November 08, 2014 @06:50PM (#8578563)
A bit shrill, I think. I don't think it's ageist to acknowledge that a lot of technologies didn't exist when older people were born and, thus, they are less likely to be familiar with them. That doesn't make them dumb, it's just an accident of history. And certainly I think that a good lawyer (and amici) should be able to explain anything the justices need to know -- the justices, whatever else you may think about them, are very intelligent people and surely capable of understanding just about anything, given sufficient time, regardless of their age. (Though this time caveat is a significant consideration. Overcoming that restriction is largely what clerks are for.)

None of this is inconsistent, though, with it's being beneficial that there are additional very smart younger people, who may be more likely to be familiar with newer technologies just in case their perspective becomes relevant.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by woofyman on Saturday November 08, 2014 @11:24AM (#8577294)
<sarcasm> Very handy to have if they have to tweet or something </sarcasm>
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rayiner on Saturday November 08, 2014 @11:34AM (#8577327)
I disagree.

This is not a case where you're digging around in the weeds trying to figure out which function does what. You don't need to be a computer scientist to understand the legally-relevant concepts in a case like this. Especially at the appellate level, where you're working with high-level concepts, and where you have people with the relevant technological background submitting amicus briefs explaining the concepts. I don't think anyone on the panel read the amicus briefs in this case and simply failed to understand what an API is.[1]

The real issue in this case is that a judge, applying the copyright law, simply does not care about whether finding API's to be copyrightable hinders interoperability or cloning of software. It's simply not legally relevant. The lynchpin of copyright is originality and creativity. Are the Java API's original and creative? That's the only relevant question.[2]

[1] And I would posit that software is easier to understand for a lay-person than a complex reinsurance arrangement or financial instrument. How would Hacker News react to the proposition that we should have specialized courts to decide financial disputes, with judges required to have a minimum of 10 years experience in Wall Street?

[2] Having written internal API's for software products, I would say they definitely are! API design is hard work that requires a lot of careful thought. Making a beautiful API is as much a creative expression as writing a sonnet or a short story, and is no less deserving of copyright protection.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DannyBee on Saturday November 08, 2014 @04:55PM (#8578264)
"The lynchpin of copyright is originality and creativity. Are the Java API's original and creative? That's the only relevant question.[2]"

This is 100% false of course. My shopping lists are creative and original, but certainly not copyrightable.

You know it's not the only question, and not even the most relevant one (which is whether the structure, sequence, and organization part of an API is the copyrightable part, or whether the literal implementation only is protected).

"[2] Having written internal API's for software products, I would say they definitely are! API design is hard work that requires a lot of careful thought. Making a beautiful API is as much a creative expression as writing a sonnet or a short story, and is no less deserving of copyright protection."

1. API's are not expressions of anything. They are literally interfaces. An outline of a story in abstract terms is not copyrightable. The actual story is. Such should it be with API's. API's are not copyrightable, their implementations are.

2. The fact that it is hard work and requires careful thought is 100% irrelevant in united states copyright law, since we have no sweat of the brow doctrine.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rayiner on Saturday November 08, 2014 @06:18PM (#8578473)
> You know it's not the only question, and not even the most relevant one (which is whether the structure, sequence, and organization part of an API is the copyrightable part, or whether the literal implementation only is protected).

To me, an "API" is just the "structure, sequence, and organization part," distinct from the implementation. I.e. you can't take a C header file and delete the parameter names, and replace all the types with typedef'ed names and get a different API. So the question is whether that (whatever you call it) is copyrightable. And under 17 USC 102, how you answer that question is to look at whether that is original and creative.

> 1. API's are not expressions of anything. They are literally interfaces. An outline of a story in abstract terms is not copyrightable. The actual story is. Such should it be with API's. API's are not copyrightable, their implementations are. 2. The fact that it is hard work and requires careful thought is 100% irrelevant in united states copyright law, since we have no sweat of the brow doctrine.

Of course, but something being hard work and requiring a lot of thought is indicative of whether it requires originality or creativity. Take, for example, the POSIX file API's. That specific combination of orthogonal function calls, the concept of passing around file descriptors as small integers, etc, is definitely a creative expression, distinct from the underlying functionality. And it's a distinct creative expression from, e.g., the Win32 file API's, which express similar functionality in a very different way.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DannyBee on Saturday November 08, 2014 @06:39PM (#8578535)
" I.e. you can't take a C header file and delete the parameter names, and replace all the types with typedef'ed names and get a different API"

Of course, if you did so, the fact that you ended up with the same API means you have removed any expressive portions, and are left with purely functional constructs and short names.

". And under 17 USC 102, how you answer that question is to look at whether that is original and creative."

Sorry, but no. The fact that something is original and creative does not, by itself, make something copyrightable in any way, shape, or form.

"Of course, but something being hard work and requiring a lot of thought is indicative of whether it requires originality or creativity."

It 100% is not indicative of this. It is hard work to compile address lists and phone numbers into the white pages. It requires a lot of thought to think through physics and math problems, and write down equations.

Neither is subject to copyright protection.

"the concept of passing around file descriptors as small integers, etc, is definitely a creative expression, distinct from the underlying functionality. "

However, as a concept, it is one completely and totally ineligible for copyright protection.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rayiner on Saturday November 08, 2014 @08:08PM (#8578715)
> Of course, if you did so, the fact that you ended up with the same API means you have removed any expressive portions, and are left with purely functional constructs and short names.

That presupposes that there is nothing expressive in the structure of the API itself, beyond the names. But the combination and structure of calls in an API is an expression in and of itself, as evidenced by the fact that the same functionality (e.g. file access) can be expressed in many different ways.

> Sorry, but no. The fact that something is original and creative does not, by itself, make something copyrightable in any way, shape, or form.

I didn't say it was the only requirement for copyrightability. There's obviously the exclusions in 17 USC 102(b). But in addition to the "work of authorship" and "fixation" requirements in 17 USC 102(a), which I assume aren't in dispute, originality is what matters.

> It 100% is not indicative of this. It is hard work to compile address lists and phone numbers into the white pages.

Ditch-digging requires a lot of work too, and I'm not asserting that is creative, but I do think API design is a creative process that requires a lot of careful thought.

> However, as a concept, it is one completely and totally ineligible for copyright protection.

Sure, the concept of passing around file descriptors as small integers is not protectable in the abstract. But it's an expressive choice that, when weaved into an API, takes it beyond purely functional into a creative expression.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DannyBee on Saturday November 08, 2014 @08:17PM (#8578729)
"That presupposes that there is nothing expressive in the structure of the API itself, beyond the names. But the combination and structure of calls in an API is an expression in and of itself, as evidenced by the fact that the same functionality (e.g. file access) can be expressed in many different ways."

By this argument, everything ever, including my shopping lists are creative expression and copyright eligible.

Copyright protection in software has never extended this far, and your argument is not particularly convincing (at least to me :P)

"Sure, the concept of passing around file descriptors as small integers is not protectable in the abstract. But it's an expressive choice that, when weaved into an API, takes it beyond purely functional into a creative expression."

We're going to have to agree to strongly disagree.

By your abstract arguing, almost everything can be found to be expressive as long as it's "an expressive choice". This would extend copyright far into the realm of methods and processes.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by throwawaykf05 on Saturday November 08, 2014 @11:58PM (#8579167)
> By this argument, everything ever, including my shopping lists are creative expression and copyright eligible.

I'm not sure that necessarily follows, but if you do use creative expression in write your shopping list, why is it not copyright-eligible? Just because it's a "shopping list"? Where do you draw the line?

And what if you no creative expression is involved in writing some code... is it not covered by copyright?

Is a "Hello World" program copyright-eligible?

Is a FizzBuzz program copyright-eligible?

Is a library that implements atoi and itoa copyright-eligible?

Is a program simply implementing a detailed spec copyright-eligible?

Is a service implementing PageRank copyright-eligible?

> This would extend copyright far into the realm of methods and processes.

I'm sure you know this, but copyright expressly excludes protection for functionality (leaving that to the realm of patents), and isn't that what methods and processes are?

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by DannyBee on Tuesday November 11, 2014 @07:14PM (#8593168)
"but if you do use creative expression in write your shopping list, why is it not copyright-eligible?"

What would it mean to use creative expression to write a shopping list?

"And what if you no creative expression is involved in writing some code... is it not covered by copyright? " It is clearly not covered by copyright in that case.

I'd need to see specific code to answer the rest of your questions.

Copyright is not a binary thing. There is essentially a 'strength of protection' that goes along with it. For example, you can have copyrights on compilations of works. Your copyright does not extend to the underlying works. Anyone can copy them (assuming they otherwise have rights).

"I'm sure you know this, but copyright expressly excludes protection for functionality (leaving that to the realm of patents), and isn't that what methods and processes are?"

No.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by throwawaykf05 on Wednesday November 12, 2014 @10:01AM (#8595694)
> What would it mean to use creative expression to write a shopping list?

Make it rhyme? Interject humor? Use archaic language? :-)

The question is, of course, why would you ever bother when it's only ever going to be you who reads the shopping list? But that's not the case with APIs! APIs are made primarily for other people to read, understand and compose other programs with. If I were to design an API that I wanted other people to use (and I have), I'd try my hardest to make it as attractive as possible.

> I'd need to see specific code to answer the rest of your questions.

I did give a list of examples, but your next paragraph answers my question, in a way. I guess "hello World" is probably not copyright-eligible, but more complex programs are. My question is, what if a complex program was just a mechanical implementation of a very detailed spec?

As to the methods and processes bit, I'm not quite clear what aspect of those you fear would be covered by copyright. If it's the actual implementation, it's just the code, which is already copyrightable. If it's the functionality or the "idea" behind the code, it is explicitly excluded.

This brings me back to my general belief that copyright is not appropriate for protecting code. (Good) code is supposed to be as boring as possible! The actual creative expression in programming goes into how problems are solved, i.e. the "idea" behind the code, and that is explicitly excluded by copyright.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by dllthomas on Sunday November 09, 2014 @05:40PM (#8581156)
It would seem to me that the exemptions in 17 USC 102(b), reading its text, could certainly be interpreted so as to apply:

"In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work."

I could easily see an API being an "idea" or "method of operation". I have no idea how this squares with precedent.

Do you know, off hand, what excludes mathematics from copyrightability?

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by AnimalMuppet on Tuesday November 11, 2014 @05:58PM (#8592837)
If I understand correctly, facts can't be copyrighted. I therefore can't copyright a^2 + b^2 = c^2.

I can copyright the text of my proof, but not the fact being proved.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by dllthomas on Tuesday November 11, 2014 @08:25PM (#8593465)
That's my understanding. I'm just wondering what particular sections of the law give that out.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by pbhjpbhj on Saturday November 08, 2014 @06:31PM (#8578522)
>* the concept of passing around file descriptors as small integers, etc, is definitely a creative expression, distinct from the underlying functionality* //

If you pass the file descriptors because that looks pretty, because of the beauty of the form and not for any functional effect. And, if the same functional effect (if there is one) can be achieved in other obvious and equally functional ways, so the only reason to do it this way is aesthetic, then yes - the essential elements are creative.

Just because you can achieve the same technical outcome in a different way doesn't make this way specifically creative however.

If an obvious way to create a specific technical effect creates a specific art-like outcome too then it's probably not copyrightable. Tyre treads, say: if your tread is created to appear different and there's no other reason to make it that way then you're covered by copyright; but if they have a technical benefit and you don't have other IP protection (patent or design patent) then others are free to duplicate that design because they are allowed to generate that technical outcome and the visual "artistry" is subordinate to that it's emergent rather than being directed.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by AnthonyMouse on Saturday November 08, 2014 @04:42PM (#8578233)
> The real issue in this case is that a judge, applying the copyright law, simply does not care about whether finding API's to be copyrightable hinders interoperability or cloning of software. It's simply not legally relevant.

How is it not? Interoperability is functional. If you can't copyright function then you shouldn't be able to copyright anything necessary for interoperability.

> The lynchpin of copyright is originality and creativity. Are the Java API's original and creative? That's the only relevant question.

That obviously isn't the only question, otherwise you could copyright anything which is patentable and get 95 years of monopoly rather than 20.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by nitrogen on Saturday November 08, 2014 @12:53PM (#8577588)
simply does not care about whether finding API's to be copyrightable hinders interoperability or cloning of software.

That is exactly why a legal professional is the wrong person to decide the issue. I've written plenty of APIs myself, and when it comes to interoperability, anybody should be free to reimplement the same interfaces, no matter how creative my design. Anything else would destroy competition in the software industry and promote a virtual dystopia of vendor lock-in.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rayiner on Saturday November 08, 2014 @02:06PM (#8577827)
> [A]nybody should be free to reimplement the same interfaces, no matter how creative my design. Anything else would destroy competition in the software industry and promote a virtual dystopia of vendor lock-in.

But that isn't a technical argument. If it had some empirical support it might be an economic one, but it's mostly just an ideological argument. One that, I might add, many software engineers would disagree with.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by nitrogen on Sunday November 09, 2014 @04:00AM (#8579445)
I'd like to meet one of these hypothetical "many software engineers" whose political opinions are so destructive to their own field.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rayiner on Sunday November 09, 2014 @09:06AM (#8579915)
Not practicing anymore, but I had those political views while I was working as an engineer. I simply don't believe you have a blanket right to inter operate without the consent of the creator. I bet you'll find plenty in companies that actually create and sell software as their business model.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by nitrogen on Monday November 10, 2014 @12:48AM (#8582192)
I simply don't believe you have a blanket right to inter operate without the consent of the creator.

The courts have regarded interoperability as a fair use in the past. https://en.wikipedia.org/wiki/Sega_v._Accolade

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by musesum on Saturday November 08, 2014 @12:21PM (#8577489)
Seems like a tradeoff between fluid intelligence and pattern recognition. In my 20's it was easier to pick up new concepts, with longer short term memory. In my 50's, I have acquired more patterns to apply. The downside, when I was younger, was going down blind alleys that wound up as a dead ends. The downside, when I got older, is misapplying an old pattern instead of synthesizing a new one. That's why I liked working with older people, in my 20's, and now working with younger people. To balance both tradeoffs.

The Supreme Court spends much of its time interpreting the patterns that are laid out in the constitution and laws passed by congress. Sometimes it synthesizes a new pattern, which will be interpreted for the next 10's or 100's of years.

For copyright, there is some value in recalling patterns from the last few decades. For example, the film industry thought that TV and later VHS would kill their business. Another is when the music industry thought that radio, cassette tapes, and MP3 files would kill their business.

The problem of employing experts as the final judge is their bias towards a particular pattern. The time spent going deep in a particular field would mean that they have less time to go broad across all fields. IMO, how to benefit US commerce is about as broad as it gets.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by WildUtah on Saturday November 08, 2014 @12:16PM (#8577477)
You don't want a special purpose court with supposed experts running anything. We have a special purpose patent court with technically experienced experts and they're the ones with the agenda to destroy the startup and independent software ecosystem by expanding patents to cover every aspect of software.[0]

[0]arstechnica.com/tech-policy/2012/09/how-a-rogue-appeals-court-wrecked-the-patent-system/

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by kchoudhu on Saturday November 08, 2014 @11:57AM (#8577417)
People from their generation got us to the moon and birthed the internet.

What have we done recently?

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by musername on Saturday November 08, 2014 @03:06PM (#8578001)
The expert-witnesses are ment to explain the problems in laymen-terms, while the court is to precide over the judicial implications given by the law that are a supposed as a level baseline. If the expert would be judge directly, he'd need expertize in law or possibly require judicial expert-witness. The Jury is supposed to level bias. Industry experts in politics is more sensical, as legislature is where by definition speciallized law is written. They are littered with economic opinions, not to say business sock puppets, already, while judges are merely incompetent on technical matters atop being burdened with - let's say - type-unsafe law code. This happens already of course, but there's little opportunity for activist, apparently.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by woofyman on Saturday November 08, 2014 @11:10AM (#8577254)
Why is the average age of the Supreme Court justices relevant ?
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by waterlesscloud on Saturday November 08, 2014 @11:16AM (#8577267)
How could a group with exceptionally sharp minds who have lived through 7 decades of intense technological and social change possibly have better perspectives than people who have lived through 2?
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by baldfat on Saturday November 08, 2014 @11:19AM (#8577277)
They all are EXTREMELY intelligent people! BUT the issues presented can be lost and then we are dependent on the staff of the justices who explain issues and then the bias of the people "educating" the justices have a HUGE influence on the justices.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by musername on Saturday November 08, 2014 @03:17PM (#8578022)
Is it not the staff, but expert-witnesses? Of course the influence of the technical advisory is subjective, so is the judge's. Arguably, more subjectivity levels out the preciseness of the judgement, it's a compromise, but certainly not unwelcome, when jury is invited to weigh out bias with it's own necessarily biased opinion. You can't get that out of the equation, because ...
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by jofer on Saturday November 08, 2014 @11:22AM (#8577287)
I agree, the ageism implied by the OP is rather disappointing. I'm relatively young (mid-30's), but the persistent implications that anyone over 40 is technical inept is rather infuriating.

Supreme court justices are (hopefully) legal experts, not technical experts. Having younger supreme court justices doesn't change that _at all_. I don't know of many lawyers that know what an API is.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by bstrand on Saturday November 08, 2014 @11:25AM (#8577301)
Good question. It probably is not relevant. I presume it's predicated on the notion that olds are generally less tech savvy (and therefore less capable of fairly & reasonably adjudicating technology cases.)

Sarah Jeong has written thoughtfully on whether justices need be tech savvy: http://sarahjeong.net/2014/04/23/scotus-is-bad-at-computers-...

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by gioele on Saturday November 08, 2014 @11:38AM (#8577353)
> We need a new legal system for arbitrating disputes in technical disciplines overseen by a panel of technical experts.

The good thing about non-technical courts is that they force the parties to explain what is at stake in terms that every intelligent person can understand. This process is very important because it can highlight things that are often assumed by people in the trade. It is the law equivalent of "rubber duck" debugging.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by Joeri on Saturday November 08, 2014 @11:08AM (#8577244)
The problem is not with the legal system, it's with the lawmaking system. Bad laws produce bad lawsuits which produce bad rulings. The fundamental problem here is IP legislation, and how poorly it was written. Or maybe the problem is one level deeper, and it's actually with the electoral system and how it selects for inadequate lawmakers.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by rodgerd on Sunday November 09, 2014 @04:37PM (#8580993)
A general purpose court with a 70 year old judge ruled against Oracle after the judge learned Java programming to understand the arguments better.

A specialised court notorious for blindly enforcing tighter interpretations of IP laws reversed the decision.

You might want to try drawing your examples from reality, not prejudice.

Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by pla3rhat3r on Saturday November 08, 2014 @11:15AM (#8577264)
It just means the people arguing this case need to explain the technology in a way they can understand it. Age has nothing to do with this.
Re:Computer Scientists Ask Supreme Court to Rule APIs Can’t ... by indymike on Saturday November 08, 2014 @11:37AM (#8577342)
Actually, this is perfect for the Supreme Court because a court set precedent aside with a rather novel decision. The issue is not a matter of technology, it's a matter of law. I think the court knows what it is doing.