News for hackers. Stuff that matters.
Re:Google’s copying of the Java SE API was fair use [pdf] by btilly on Monday April 05, 2021 @02:32PM (#26702750)
While the result is a big relief, I think it's not as decisive as I'm noticing some headlines (and commenters) are claiming.

It is even less decisive than you're saying.

The fact that the Supreme Court decided not to overturn the decision of the Court of Appeals for the Federal Circuit that APIs are copyrightable means that binding precedent on every court except the Supreme is that they are. And for fair use, one of the statutory factors is the "effect" of the copying on the "market for or value of the copyrighted work."

That said, this case does establish a precedent that if your copying of an API is primarily for purposes of matching an interface so that developers can reimplement it, you're in fair use territory:

The fact that one statutory factor points one way doesn't stop another from pointing the other. And part of their decision is the conclusion that Google's copying increased the value of Java. That will generally not be true when APIs get copied.

In particular if I am trying to create a product that competes with yours, and I copy your API for the purpose of interoperability, I'm going to have an uphill battle claiming fair use. Because my product directly reduces the market for your product.

To name some historically important examples, Microsoft copied the APIs for JavaScript from Netscape, Microsoft copied APIs from Lotus 1-2-3 for Excel, and Wine copied APIs from Windows for Linux. The outcomes famously were that Netscape went out of business, Lotus 1-2-3 was discontinued, and Linux became somewhat more viable.

Re:Google’s copying of the Java SE API was fair use [pdf] by dragonwriter on Monday April 05, 2021 @04:26PM (#26704215)
> The fact that the Supreme Court decided not to overturn the decision of the Court of Appeals for the Federal Circuit that APIs are copyrightable means that binding precedent on every court except the Supreme is that they are

No, it doesn’t. Because the Court expressly declined to examine the question, the CAFC decision is binding only where it would have been without the Supreme Court decision, i.e., those courts bound by the CAFC’s interpration of how Ninth Circuit law applies. As it turns out, that is exactly zero courts.

The reason the Supreme Court often likes to find the narrowest grounds possible for a decision is to avoid making more binding case law than is called for; giving the lower court rulings on all questions not addressed (including those the Supreme Court explicitly avoids) the same binding effect as the actual Supreme Court holding would defeat the purpose, and it is very much not how things work.

Re:Google’s copying of the Java SE API was fair use [pdf] by DannyBee on Monday April 05, 2021 @07:01PM (#26705763)
It was zero courts before, too, no?

CAFC does not have natural jurisdiction over copyright and thus always applies circuit law.

Here, this was also a 3-judge panel of the federal circuit, and en banc review was denied.

Those decisions are already not binding on future 3-judge panels IIRC (it's been a while, honestly), and definitely not binding on the circuits

Re:Google’s copying of the Java SE API was fair use [pdf] by dragonwriter on Monday April 05, 2021 @07:06PM (#26705808)
> It was zero courts before, too, no?

Right, and I think this played an important role in why the Supreme Court ducked API copyrightability; they’d rather not do so absent a binding lower circuit decision, or especially a conflict between circuits, preferring to let the issue percolate (and also provide Congress more time to intervene) of there is another basis dor resolving particular cases with less sweeping impact.

Re:Google’s copying of the Java SE API was fair use [pdf] by curt15 on Monday April 05, 2021 @02:44PM (#26702882)
>The fact that the Supreme Court decided not to overturn the decision of the Court of Appeals for the Federal Circuit that APIs are copyrightable means that binding precedent on every court except the Supreme is that they are.

Federal Circuit's ruling would only be precedent in the 9th circuit. As it does not have original jurisdiction in copyright disputes (only patent cases), it doesn't supercede any copyrightability rulings in other circuits, for instance the 1st circuit's holding in Lotus v Borland that the Lotus macros were not copyrightable as a "method of operation". And today's opinion cites Lotus v Borland several times even though the original 1996 Supreme Court case was deadlocked at 4-4.

Re:Google’s copying of the Java SE API was fair use [pdf] by wtallis on Monday April 05, 2021 @02:57PM (#26703093)
> Federal Circuit's ruling would only be precedent in the 9th circuit.

I think it's even narrower than that: the Federal Circuit's ruling on non-patent aspects of the case isn't binding precedent outside of Oracle v. Google. District courts in the Ninth Circuit and the appeals court are free to ignore the Federal Circuit ruling in future cases and look to only rulings from the Ninth Circuit and Supreme Court as binding precedent.

Re:Google’s copying of the Java SE API was fair use [pdf] by DannyBee on Monday April 05, 2021 @07:07PM (#26705826)
The federal circuit's ruling is not precedent or binding in the 9th circuit. Because of it's lack of jurisdiction, it doesn't supersede anything, not just "other circuits" They have no subject matter jurisdiction over copyright, and so they only apply pre-existing regional law. Their decisions on that pre-existing regional law have no force within that circuit.

This is similar to when federal courts have to apply state law.

Re:Google’s copying of the Java SE API was fair use [pdf] by mdale on Monday April 05, 2021 @04:07PM (#26703968)
Wine was not really as much of an organized commercial endeavor so was not as much of a target
Re:Google’s copying of the Java SE API was fair use [pdf] by Xylakant on Monday April 05, 2021 @07:05PM (#26705801)
You could sue wine to take a swing at everyone building on wine. Valve/Steam for example.
Re:Google’s copying of the Java SE API was fair use [pdf] by btilly on Monday April 05, 2021 @03:13PM (#26703292)
Federal Circuit's ruling would only be precedent in the 9th circuit.

No, not only 9th circuit.

The Court of Appeals for the Federal Circuit is binding nationwide. And if the case includes claims about patents and/or trademarks, even if those specific claims are thrown out, then the Court of Appeals for the Federal Circuit becomes the court that the case is appealed to.

Which is how this particular case wound up there in the first place.

Re:Google’s copying of the Java SE API was fair use [pdf] by wtallis on Monday April 05, 2021 @03:38PM (#26703596)
When ruling on aspects of a case that fall outside of their subject matter jurisdiction (eg. copyright rather than patents), the Federal Circuit is supposed to follow the local circuit's precedent, ie. rule how they think the Ninth Circuit would have ruled on those issues. And my understanding is that the Federal Circuit's rulings on eg. the copyright aspects of a case like this do not overturn Ninth Circuit copyright precedent and do not establish new copyright precedent anywhere, not even the Federal Circuit (since in future cases they will again be required to apply the relevant local circuit's copyright precedents as they exist at that time).

The Federal Circuit's copyright decision is binding on the parties to the case at hand, but the precedent for future cases is non-binding at best.

This was one of the arguments that the FSF and SFLC put forth in their amicus brief recommending that the Supreme Court not take up Google's appeal of the API copyright question:

> The court below predicted, on the basis of no compelling evidence, that the Ninth Circuit would depart from settled existing law in a novel direction which, as amici supporting the petition have said at length, would be destructive alike of commercial certainty and freedom to implement, thus inhibiting the progress of science and the useful arts. Neither the Ninth Circuit nor any other regional Court of Appeals is likely to defer to this improbable supposition, so the error is largely self-limiting. Such erroneous predictions of other courts’ holdings are not a suitable employment of this Court’s scarce resources in review by certiorari.

Re:Google’s copying of the Java SE API was fair use [pdf] by dctoedt on Monday April 05, 2021 @04:18PM (#26704111)
IP lawyer here — @wtallis's summary is how I understand the impact of the Federal Circuit decision as well.
Re:Google’s copying of the Java SE API was fair use [pdf] by dragonwriter on Monday April 05, 2021 @04:30PM (#26704271)
> No, not only 9th circuit.

Not even the 9th Circuit. For cases arising from thr 9th Cir., 9th Cir. case law binds the CAFC, not the other way around, on issues that are outside ofnthe subject-matter for which the CAFC has nationwide jurisdiction.

> The Court of Appeals for the Federal Circuit is binding nationwide

No, it’s decisions are only binding nationwide on the issues within its special jurisdiction, which copyright is not. On other issues, it is instead bound by the case law of the circuit that would otherwise be responsible for the case, and notionally is just an interpreter of that circuit's case law. It’s decisions on those collateral matters on cases brought before it because they also touch on one of the issues reserved to the CAFC aren’t binding on any other court.

Re:Google’s copying of the Java SE API was fair use [pdf] by AlexCoventry on Monday April 05, 2021 @04:43PM (#26704438)
> issues within its special jurisdiction

How are those issues defined?

Re:Google’s copying of the Java SE API was fair use [pdf] by phonon on Monday April 05, 2021 @04:52PM (#26704570)
Re:Google’s copying of the Java SE API was fair use [pdf] by AlexCoventry on Wednesday April 07, 2021 @10:47AM (#26725717)
Thanks.
Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Monday April 05, 2021 @05:23PM (#26704903)
Lotus' failure was more because they failed to port to Windows, betting instead on OS/2.

Lotus was at a crossroads. DOS was obsolete, was the future OS/2 or Windows? They chose OS/2.

Lotus was a big, cash rich company at the time. Their fatal error was not realizing they should have ported 1-2-3 to both OS/2 and Windows. Then they would have been secure regardless of which prevailed.

Re:Google’s copying of the Java SE API was fair use [pdf] by hyperman1 on Tuesday April 06, 2021 @04:33AM (#26709491)
At that point(1989), the future was less clear-cut than Windows vs OS2. Windows was more a graphical shell for DOS than a real OS, and there were other graphical shells for DOS. From the top of my head: I vaguely remember GEM, I have used one from Tandy. There was something else installed on our school computers, Dynamic Environment or something . Windows before 3.0 (1990) was inferior to a lot of these DOS shells.

If the choice was between 2 options, 'both' might be a viable response. But 3 or more, especially with a market expectancy that everything DOS-based would disappear?

Re:Google’s copying of the Java SE API was fair use [pdf] by randomswede on Tuesday April 06, 2021 @07:10AM (#26710458)
You may be thinking of DesqView? It provided some level of virtualisation and multi-tasking, if you had a competent-enough CPU. Eventually, there was also DesqView/X which allowed you to export DOS and DesqView-aware applications over X11, which was actually kind of cool.
Re:Google’s copying of the Java SE API was fair use [pdf] by hyperman1 on Tuesday April 06, 2021 @08:43AM (#26711084)
I completely forgot about DesqView. Never used it of saw it, but yes, that was another well-known one.
Re:Google’s copying of the Java SE API was fair use [pdf] by WorldMaker on Wednesday April 07, 2021 @01:21PM (#26727890)
Right, and Microsoft was still putting so much development work into OS/2 in 1989 that there was still some sort of feeling that OS/2 was possibly the future of Windows. (OS/2 development kits were shipped from Microsoft with Microsoft branding prominently on them right up until the OS/2 3.0 [WARP] split and the origins of Windows NT.)

In hindsight it is much more obvious that Microsoft's involvement in OS/2 was something of a trojan horse to fund early NT development and a short-term hedge in case people did trust the IBM brand more than the Microsoft brand, but at the time it was much more confusing.

Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Tuesday April 06, 2021 @02:35PM (#26715572)
There was little doubt at the time that DOS based systems were rapidly becoming obsolete, and the future would be 32 bit Windows or OS/2.
Re:Google’s copying of the Java SE API was fair use [pdf] by dragonwriter on Monday April 05, 2021 @11:34PM (#26707706)
> Lotus was a big, cash rich company at the time. Their fatal error was not realizing they should have ported 1-2-3 to both OS/2 and Windows. Then they would have been secure regardless of which prevailed

That’s...optimistic. The transition to GUIs undermined a major hold they had, which was user-familiarity-lock-in. That transition was going to be an opening no matter what, especially for a competitor that also controlled the platform that won out underneath the application.

Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Tuesday April 06, 2021 @01:16AM (#26708146)
Lotus bet the farm on OS/2. Not being on Windows made it an easy decision for customers to buy Excel.

Lotus was bigger than Microsoft for most (all?) of the 1980s.

Wordstar was another company that failed to understand the shift to GUIs.

Of course, Wordstar had another major marketing problem. Despite its dominance, nobody knew the name of the company (MicroPro) that made it. Far too late they realized the mistake and changed the company name to Wordstar. Microsoft never made that mistake.

Re:Google’s copying of the Java SE API was fair use [pdf] by hnick on Monday April 05, 2021 @07:03PM (#26705783)
Lotus 1-2-3 was on Windows so I think I am missing some context here around version differences?
Re:Google’s copying of the Java SE API was fair use [pdf] by __d on Monday April 05, 2021 @07:43PM (#26706145)
Timing, IIRC. Lotus was late to Windows, opening the door for Excel.
Re:Google’s copying of the Java SE API was fair use [pdf] by hnick on Monday April 05, 2021 @07:54PM (#26706226)
Yeah it seems to be 1989 v 1991 based on the wiki but it also sounds like there might be some version differences. 2 years was a long time back then.
Re:Google’s copying of the Java SE API was fair use [pdf] by jolux on Monday April 05, 2021 @07:58PM (#26706256)
It's still a long time! You try being two years later to a major market than Microsoft and still beating them. How often has that happened?
Re:Google’s copying of the Java SE API was fair use [pdf] by jychang on Tuesday April 06, 2021 @12:53AM (#26708041)
Windows Mobile - iPhone Tablet PC - iPad Internet Explorer - Google Chrome MSN Messenger - Facebook Messenger, iMessage, etc Microsoft Band - Apple Watch Zune Pass (2006) - Spotify (2009, 2011), Apple Music, etc Skype - Zoom Hotmail - Gmail
Re:Google’s copying of the Java SE API was fair use [pdf] by thereddaikon on Tuesday April 06, 2021 @01:59PM (#26715177)
Windows Mobile may have been there before iOS but it came after Blackberry and palm. iOS and iPhone was also revolutionary. Smartphones changed substantially from that.

Internet Explorer wasn't the first browser on the market but by the time Chrome had come around Microsoft had let it languish and it became pretty awful. For a long time Microsoft had convincingly won the browser war.

Same with MSN messenger, it didn't keep up. And nobody has ever decisively won that chat app war anyways .

Smartwatches have been around for a very very long time. What Apple did was get smartphone integration right.

Zune Pass isn't a streaming service, its a DRM laden online music store. So more akin to iTunes than Spotify or Apple Music. And it was very late to the game.

Re:Google’s copying of the Java SE API was fair use [pdf] by fnord123 on Tuesday April 06, 2021 @03:32AM (#26709096)
Skype -> Whatsapp, Zoom
Re:Google’s copying of the Java SE API was fair use [pdf] by Gaelan on Tuesday April 06, 2021 @12:42AM (#26707999)
Windows Mobile/iOS? Arguably Office and Google Docs.
Re:Google’s copying of the Java SE API was fair use [pdf] by jolux on Tuesday April 06, 2021 @12:50AM (#26708030)
Google Docs was released 20 years after Office, after Office had already killed all the rest of its competition in the early 90s.

iOS is a good example though. Windows Mobile had not yet come to dominate the market.

Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Monday April 05, 2021 @05:25PM (#26704925)
Netscape went out of business because their browser crashed far more frequently than Explorer. I've heard all the sob stories, but I was sick of the constant crashing of Netscape, and so tried Explorer. Explorer crashed too, but not nearly as often.
Re:Google’s copying of the Java SE API was fair use [pdf] by unreal37 on Monday April 05, 2021 @10:58PM (#26707512)
Hmm, I worked at a large company in 1995 as a web dev, and they were paying a license fee "per copy" of Netscape Navigator. I distinctly remember this, because we had 10,000 licenses. But we did get phone support with that, and I talked to Netscape's help desk a few times with various issues I faced as a developer.

Commercial users were paying for Netscape in 1995. It was only free for personal use. Even articles from 1996 mention the cost of Netscape as $49. [1]

So at least part of the reason IE displaced Netscape was that it was free for enterprises. And Netscape was not, until it was too late.

[1] https://www.fastcompany.com/27743/nothing-netscape

Re:Google’s copying of the Java SE API was fair use [pdf] by mceachen on Monday April 05, 2021 @05:34PM (#26705002)
FWIW, Netscape got bought out by AOL, but not before it spun off Mozilla. https://en.wikipedia.org/wiki/Netscape

It may be hard to believe, but the first iteration of Internet Explorer on Macintosh (back on System 8) was __solid__. IE, at least on PowerMacs, was way faster and more reliable than either NCSA Mosaic or Navigator.

Re:Google’s copying of the Java SE API was fair use [pdf] by kibwen on Monday April 05, 2021 @06:45PM (#26705619)
Hell, AOL still runs Netscape as a discount ISP, same logo since 1999 and everything: https://isp.netscape.com
Re:Google’s copying of the Java SE API was fair use [pdf] by torstenvl on Tuesday April 06, 2021 @08:02AM (#26710791)
God that's a beautiful website. Loads fast. Not too many graphics. Nothing moves unless I tell it to.
Re:Google’s copying of the Java SE API was fair use [pdf] by collinmanderson on Tuesday April 06, 2021 @10:16AM (#26712014)
> Netscape got bought out by AOL

That makes it sound like Netscape had no say in the matter. Netscape sold itself to AOL.

Re:Google’s copying of the Java SE API was fair use [pdf] by Talanes on Tuesday April 06, 2021 @11:34PM (#26720325)
"Bought out" is a common enough way to describe any company sale. "Sold itself" introduces way more unnecessary sub-textual baggage just by being a more unusual construction.
Re:Google’s copying of the Java SE API was fair use [pdf] by tinus_hn on Monday April 05, 2021 @05:56PM (#26705204)
Microsoft had FrontPage create pages that crashed Netscape.
Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Monday April 05, 2021 @06:28PM (#26705455)
Netscape crashing on a web page is Netscape's fault.

Similarly, if the D compiler crashes when compiling a D source file, it's the D core team's fault.

Re:Google’s copying of the Java SE API was fair use [pdf] by alasdair_ on Tuesday April 06, 2021 @12:13AM (#26707885)
If the people that make the OS whose APIs you are reliant on, are also the ones trying to make your code crash, I'd bet most of us would end up with crashing code.
Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Tuesday April 06, 2021 @01:01AM (#26708084)
I've never heard of any evidence that Microsoft planted:

    if (NetscapeIsRunning()) corrupt_data();
in their OS API calls. If they had, I'm sure it would have come out at the anti-trust trial, and would have made it an open and shut case. Did that happen?

As I recall, the anti-trust case revolved around Microsoft including IE for free with Windows, not sabotage. (Of course, every OS comes with a free browser these days. Even my Kindle.)

Re:Google’s copying of the Java SE API was fair use [pdf] by michaelt on Tuesday April 06, 2021 @07:16AM (#26710492)
The claim by tinus_hn is that FrontPage - Microsoft's HTML editing tool - created pages that crash Netscape.

While it would arguably be Netscape's fault if Netscape actually crashes (rather than simply failing to display a malformed input) at that time in the browser wars there were plenty of energy going into creating incompatible new 'features' - such as Microsoft's own JavaScript competitor, VBScript [1], vector imaging format (AutoShapes) and animation tags (DHTML)

And Microsoft did intentionally sabotage competitors products in the 1990s with approval from the highest levels of the business - such as DR-DOS [2].

So while I'm not aware of any claims Microsoft sabotaged the OS to make Netscape crash, they'd sabotaged the OS to make other competing products crash, and they certainly added a lot of 'features' so web pages wouldn't render right on Netscape.

[1] http://www.gbengasesan.com/fyp/43/ch5.htm [2] https://en.wikipedia.org/wiki/AARD_code

Re:Google’s copying of the Java SE API was fair use [pdf] by WalterBright on Tuesday April 06, 2021 @02:32PM (#26715545)
I know about the AARD episode, and Microsoft lost a lawsuit over it, which was the right result.

There's zero evidence Microsoft sabotaged Netflix.

There's zero evidence Netscape crashed for any reason other than buggy Netflix code. Making a web page that crashes Netflix is a bug in Netflix. Microsoft is under zero obligation to work around Netflix bugs.

Re:Google’s copying of the Java SE API was fair use [pdf] by dpe82 on Monday April 05, 2021 @06:22PM (#26705403)
Netscape produced a browser that could be crashed by a malformed page.
Re:Google’s copying of the Java SE API was fair use [pdf] by tinus_hn on Monday April 05, 2021 @07:07PM (#26705823)
> Explorer crashed too, but not nearly as often.
Re:Google’s copying of the Java SE API was fair use [pdf] by cloudwizard on Monday April 05, 2021 @08:44PM (#26706655)
Netscape was not selling their browser so that did not matter. I worked at a startup that used their server. We wanted to pay for it but they would not invoice us. Just sending money without an invoice would have been a donation. I sat for hours on their customer support line trying to get an invoice but they never sent one until they went out of business.
Re:Google’s copying of the Java SE API was fair use [pdf] by kbrisso on Monday April 05, 2021 @09:40PM (#26707047)
I worked on Netscape Enterprise Server it had JavaScript as the scripting language. Did you work on that? Before NodeJS....
Re:Google’s copying of the Java SE API was fair use [pdf] by unreal37 on Monday April 05, 2021 @10:59PM (#26707521)
They absolutely did sell their browser to enterprises. It was only free for personal use.
Re:Google’s copying of the Java SE API was fair use [pdf] by colejohnson66 on Tuesday April 06, 2021 @09:38AM (#26711583)
I think that’s what cloudwizard is saying. They knew that Netscape cost money for professional use, but in trying to get an invoice to actually pay for it, Netscape did nothing.
Re:Google’s copying of the Java SE API was fair use [pdf] by unreal37 on Friday April 09, 2021 @03:09PM (#26754743)
I worked at a company in 1994 that had 10,000 licenses to Netscape Navigator. I had a support person I could call. So on some scale, there was definitely a way to send them money.
Re:Google’s copying of the Java SE API was fair use [pdf] by ekianjo on Monday April 05, 2021 @06:40PM (#26705564)
Yup, I can clearly remember Netscape crashing very very often. It was definitely the worse browser.
Re:Google’s copying of the Java SE API was fair use [pdf] by Firehawke on Monday April 05, 2021 @10:12PM (#26707231)
Exactly this. There's a lot of historic revision that says IE was never good, but there was a significant chunk of time around IE2 and IE3 where it slaughtered Netscape on Windows. Better performance, less crashing all around.

IE4 is where ActiveX and browser bloat started to become more obvious, then IE5 was an improvement again.. but we were only a short time from the launch of what would become Firefox. By that point, people were tired of the constant IE issues.

Re:Google’s copying of the Java SE API was fair use [pdf] by utucuro on Tuesday April 06, 2021 @12:55AM (#26708050)
At some point, I was using IE 5, then IE 5.5, then Opera and then Firefox 0.8! Used some Neoplanet as well, but I cannot remember when anymore, must have been before Opera... IE 5.5 was great at the time, though mouse gestures and tabs on Opera were better.
Re:Google’s copying of the Java SE API was fair use [pdf] by davegauer on Tuesday April 13, 2021 @11:12AM (#26793314)
Bingo and I distinctly remember when IE's CSS support was significantly better than Netscape's at a crucial point in time when it really mattered to nascent Web design and development.
Re:Google’s copying of the Java SE API was fair use [pdf] by atkbrah on Tuesday April 06, 2021 @01:09AM (#26708123)
Explorer also launched a lot faster than especially the late versions of netscape.
Re:Google’s copying of the Java SE API was fair use [pdf] by icedchai on Monday April 05, 2021 @08:03PM (#26706294)
Yep. Netscape crashed at least every 30 minutes.
Re:Google’s copying of the Java SE API was fair use [pdf] by kmeisthax on Tuesday April 06, 2021 @11:25PM (#26720270)
I should point out that in the Ninth Circuit, there's already plenty of strong, citeable precedent in favor of fair use for the purpose of interoperability; separate from the purpose of programmer convenience that the Supreme Court endorsed. It's my opinion that programmer convenience is strictly wider than interoperability. The only reason why SCOTUS needed to rule this way is:

1. Google did not copy Java APIs strictly for the purpose of interoperability (they specifically did not want interoperability with other Java environments).

2. Ninth Circuit court precedent does not apply in the Federal Circuit, which is the only reason why Oracle even had a leg to stand on.

Had Oracle not had a patent claim in this lawsuit, it would have wound up in the Ninth Circuit, we would have gotten another respectable decision limiting software copyright from that court, and the only thing SCOTUS would have had to have done would have been to deny cert to Oracle after they lost. It's entirely due to the Federal Circuit not respecting basic concepts of how software works and ruling on something that shouldn't have been in their jurisdiction that we got here.

Re:Google’s copying of the Java SE API was fair use [pdf] by scomp on Monday April 05, 2021 @07:14PM (#26705880)
What about Microsoft J# or Microsoft J++? A directly relatable example.
Re:Google’s copying of the Java SE API was fair use [pdf] by ConceptJunkie on Tuesday April 06, 2021 @12:05PM (#26713574)
To be fair, Netscape lost because their product, at the time, was inferior. Netscape blew IE out of the water at first, but IE kept getting better. Netscape 3 was excellent, but when IE 4 came out, it was just better. Then came Netscape 4. 'Nuff said.

Lotus couldn't make the transition to Windows, and so lost to Excel (and perhaps Quattro Pro... it's been a long time and I don't remember details). This had nothing to do with copying APIs. Of course, it probably had everything to do with Microsoft's anti-competitive advantage by having access to Windows internals and undocumented features, but that's another matter.

Re:Google’s copying of the Java SE API was fair use [pdf] by halfmatthalfcat on Monday April 05, 2021 @04:11PM (#26704022)
I wonder how this would effect things like Preact too, which for operability sake, uses the exact same API as React.
Re:Google’s copying of the Java SE API was fair use [pdf] by anamexis on Monday April 05, 2021 @04:14PM (#26704059)
In that specific example, I don't think it would really affect them, since both React and Preact are MIT licensed.
Re:Google’s copying of the Java SE API was fair use [pdf] by Natanael_L on Monday April 05, 2021 @06:34PM (#26705511)
One of the issues here is that it's not even clear under which license the API should be covered. Does the existing software license also cover the API, or must it be explicitly defined?

What happens when an API is co-created by different software developers which each creates their own software under different licenses, through communications which themselves aren't explicitly licensed (like over email lists), and then summarize what they agree on in text instead of code (like the RFC process)?

At no point have either one of them explicitly given permission to use their respective contributions under another license. Even if they agree that the RFC text is public domain, that technically do not extend to implementations of the API which it describes (as those are different works!). And there exists no official reference code with legal approval from all contributors, whose license could be adopted by other developers.

It would be such a mess...

Re:Google’s copying of the Java SE API was fair use [pdf] by thaumasiotes on Monday April 05, 2021 @06:51PM (#26705674)
> both React and Preact are MIT licensed.

Huh, I had no idea the React license wasn't still "you're free to use React unless you ever assert a patent against Facebook".

Re:Google’s copying of the Java SE API was fair use [pdf] by elyobo on Monday April 05, 2021 @07:10PM (#26705850)
Concern about the licensing was eventually sufficient that they resolved it a few years back.
Re:Google’s copying of the Java SE API was fair use [pdf] by 0df8dkdf on Monday April 05, 2021 @04:17PM (#26704093)
Not a lawyer, seems like this case will hold precedence then. The whole idea of copy righting an API is insane.
Re:Google’s copying of the Java SE API was fair use [pdf] by collinmanderson on Tuesday April 06, 2021 @09:57AM (#26711795)
DOS also copied APIs from CP/M (though that was before Microsoft bought it I assume)
Re:Google’s copying of the Java SE API was fair use [pdf] by bryanrasmussen on Wednesday April 07, 2021 @03:01AM (#26721308)
Can any of those companies copying APIs in the past be sued now due to this precedent?