Developer Freedom At Stake As Oracle Clings To Java API Copyrights

http://www.techcrunch.com/2013/03/30/developers-should-care-about-oracles-upcoming-appeal-of-the-google-lawsuit

by mitmads • 13 years ago

77 65 13 years ago

cft2• 13 years ago

Choosing Java and Dalvic was probably a mistake for Android.

Not buying Sun was the mistake. $7B is all that would've taken (less if they sold the os and hardware division) to make the computing world a better place.

smrtinsert2• 13 years ago

7B is pocket change to them, completely agree. I was shocked to hear they let it pass iirc. I figured they were playing hardball and it just blew up in their face.

trust-me• 13 years ago

IMHO you're over simplifying. Oracle was better positioned to capitalize on Sun assets, so they were likely to pay more than Google. Microsoft or Apple may have decided to bid to prevent Google from acquisition. Merging with a huge enterprise is always painful.

pekk• 13 years ago

Question: will this cost Google $7B?

comex• 13 years ago

Not necessarily. If the judgement that APIs are not copyrightable is upheld (which is a big if), the computing world will be a better place than it would be if Google had managed to avoid the question.

cageface5• 13 years ago

I've thought this myself lately but what alternatives did they really have? The only other real alternatives are C++ and C#, which are both problematic for different reasons.

I wouldn't mind seeing a new mobile OS build around Go but it's way too late for a change that fundamental for Android. For better or worse Java & Android are married now.

fauigerzigerk4• 13 years ago

"what alternatives did they really have?"

JavaScript

_ea1k• 13 years ago

Java might have been, but I am not sure about Dalvik. Without the Java language conversion, I doubt Oracle would have ever bothered to attack Dalvik.

On the other hand, so far this case has been nothing but a boondoggle for Oracle. It seems that is unlikely to change at this point.

rdtsc2• 13 years ago

If they had to redo it today, what could it be instead?

* Javascript -- I hate the language, it has enough warts to make it unpalatable

* Dart -- I can see it, that would be great, still kind of new though

* Python -- I understand they could have done it, but it was a political decision not to (at least according to Guido's remark during one of the PyCon's), performance might not be up to par on some devices

* Go -- too low level perhaps, but it would be cool

cft2• 13 years ago

Go, C/C++, but in the ideal world- Python (they would have to very seriously tweak the interpreter)- imagine how easy app creation would have become with Python? They would have a huge advantage over iOS by lowering the entry thresholds for developers.

djhworld2• 13 years ago

The advantage the DVM has is it's a baseline that developers can work with instead of worrying about hardware.

This was probably very desirable to Google in 2005 as it gave them the chance to court mobile manufacturers with the promise that their operating system can be deployed across a range of devices and theoretically all apps etc should remain functional, regardless of hardware as it's the VM that's the deployment target, not the phone.

Remember that back in those days the mobile OS world was god awful, Symbian was abysmal, JavaME was broken and Windows CE....well let's not go there.

cliffu• 13 years ago

A phone in either Smalltalk or Lisp would be awesome IMO.

dlitz• 13 years ago

Did they really have to pick one language to rule them all?

It seems odd to me to design a platform that only supports one programming language. What happens when people find better ways of expressing their intent?

ceautery• 13 years ago

What a bunch of jackasses. Sometimes I think the only difference between Oracle and SCO is scale.

jacquesm• 13 years ago

> Sometimes I think the only difference between Oracle and SCO is scale.

Whenever you think that you should probably read up on both Oracle and SCO.

SCO was a dying company that tried every dirty trick in the book to blackmail the world into giving it a free ride to newfound riches based on ridiculous claims. SCO was backed behind the scenes by Microsoft simply to attack Linux which Microsoft saw as a threat to its bottom line. As such SCO was really nothing but a proxy for Microsoft in the dirtiest fight that the IT industry has ever seen.

Oracle is a very successful company that bought the assets of another dying company (SUN) in order to safeguard a line of business and in order to buy the IP rights of that dying company, which included Java.

Note that I'm not defending what Oracle is doing here but the differences between SCO and Oracle are enormous, and are certainly not limited to scale.

In many ways the Oracle case is much more dangerous because it now openly attacks a well established principle (interoperability) and Oracle actually has the resources to do real damage. For now that damage is limited to Oracle shooting in its own foot (Damaging the Java brand in a very clear and concrete way) but that could easily change.

Google has a very long standing habit of doing or buying things that are illegal (youtube, books, caching the web, images) and getting away with them because they have deeper pockets than the copyright owners or because they strike a deal when cornered.

SCO's claims aginst linux ('10's of thousands of lines') were absolutely unfounded, Oracle's claims against Dalvik seem to have at the surface at least some merit.

And Oracle is not simply going to give up on what it perceives to be its right simply because the party they believe is infringing is Google.

Still, I'm rooting for Google to win this one and for Oracle to lose this one, the consequences of the fall-out of an Oracle win would be pretty disastrous.

microtonal2• 13 years ago

SCO was a dying company that tried every dirty trick in the book to blackmail the world into giving it a free ride to newfound riches based on ridiculous claims.

Actually, ironically, it's not SCO that tried to sue every Linux vendor, but the Linux company formerly known as Caldera Systems (of Caldera OpenLinux). They purchased SCO's UNIX business and renamed themselves to The SCO Group. The real SCO was renamed to Tarantella.

It's sad, not only is the name of 'old SCO' forever associated with attacks that they did not participate in, the Linux ecosystem was actually under attack by a (former) Linux company.

fkdjs• 13 years ago

None of those things you brought up are illegal. Oracle is a scourge and just a step above SCO, but that's a pretty low bar. Making it so you designate something arbitrarily as a "language" and you can be the only princess that implements it is plain evil. Fortunately the appeal is going no where.

fruit• 13 years ago

oh god how could this happen

im so surprised

smrtinsert2• 13 years ago

Why didn't Google just buy Java, way to drop the ball.

warmwaffles• 13 years ago

Didn't have a big enough stake in it to justify the purchase of Sun. Oracle however, did have a lot riding on Java succeeding and removing the Sun Hardware division as a competitor.

fauigerzigerk4• 13 years ago

The Sun hardware division wasn't competing with Oracle at the time. I think they bought Sun because they thought it made sense to sell software + hardware and because they didn't want IBM to have Java.

If Larry Ellison hadn't underestimated the cloud trend, the takeover probably wouldn't have happened. Oracle has been very successful with its M&A activities, but this one is clearly a complete desaster.

bdunbar• 13 years ago

If Oracle gets heavy handed with Java ... doesn't that just mean it's time to use something else?

Am I missing something?

salmanapk• 13 years ago

What Java alternatives do we have other than Mono/C#?

jrockway• 13 years ago

All the other programming languages. What makes C# and Java particularly special?

microtonal2• 13 years ago

That depends on what you think is important in Java. The language? Plenty of alternatives. The virtual machine? Not so much. Or perhaps even the class library?

A1kmm• 13 years ago

The legal precedent if the case is reversed on appeal potentially extends beyond just Java; the article is essentially about the ruling that APIs can't be copyrighted, and that numerous amicus curiae briefs argued in favour of APIs being copyrightable.

If APIs can be copyrighted, it would seriously harm interoperability. For example, if the ruling holds, someone could make a payments service which replaces Paypal so seamlessly that to integrate it you can just change the 'paypal.com' string for 'competitorsbrand.com' without redoing all the work you did for Paypal integration. This would be bad for Paypal but would be great for making the market far more efficient. Similarly, if it is reversed on appeal, Wine and Mono could be considered copyright violations and sued by Microsoft.

If it extended to non-software interfaces a reversal could be even worse - imagine if the idea that turning the round wheel in front of the driver causes a car to move in the corresponding direction was a copyrighted interface? In that particular case, Copyright in the US wouldn't have expired until 1985, so other manufacturers would have needed to come up with different interfaces, and switching makes would have been hard.

jfim• 13 years ago

True. However, Oracle could argue that writing good APIs does require money and domain expertise, which could be considered non-obvious and (maybe) copyrightable. For example, look at the Java date/calendar API; it went through a complete revision and still managed to be broken.

It's a good question, however, if API designs should be copyrightable in the same fashion building blueprints are.

znowi• 13 years ago

I see Oracle as cancer of the corporate world. An old dinosaur who happened to slog into 2013. The new generation of young and socially responsible will hopefully put an end to their kind.

CurtMonash3• 13 years ago

There's no way an API should be covered by copyright, for the judge's reasons. If you can get a patent on it, good luck to you; otherwise, it's not proper IP.

Patenting an API would be like patenting a UI -- reasonable under the law. http://www.dbms2.com/2010/03/23/software-innovation-patent/ Whether the law should be changed -- as I think it should be -- to make such patents unreasonable is a separate issue.

kvb4• 13 years ago

I don't see why. There's plenty of creative discretion involved in the writing of an API. I would have expected this to be a fair use issue rather than a copyrightability issue (though IANAL).

delinka3• 13 years ago

"Fair use" is, by definition, an issue involved in copyright. But I see your point- if APIs are copyrightable, then uses of that API may be "fair use." But then someone's got to drag all the potential uses through the courts to determine what's fair use and what's not (because apparently fair use can only be determined by the courts...) I would surmise that, in this dystopian fantasy world (and I hope it remains such), 'interoperability' would be the de facto fair use and any other use of an API would legally require a license. What a nightmare.

CurtMonash3• 13 years ago

There also is discretion in how you label the fields on an order form, but good luck copyrighting one of those.

tosh• 13 years ago

Dart as a long-term replacement for Java anyone :)

GhotiFish• 13 years ago

I don't agree.

I'm fine if dart kills javascript. What it's made to do.

I'd also be fine if go/python/befunge kills java.

brown9-2• 13 years ago

While Oracle is hard to sympathize with, the actual article never elaborates on it's inflammatory statement as how "developer freedom" is at stake (or what that phrase even means).

delinka3• 13 years ago

I can't tell if this is criticism alone, or if you're also asking the question. It seems these articles and discussions assume that the reader is all-knowing when it comes to the IP issues developers could face in their careers. Allow me to attempt to fill in the gaps.

When you write code, in the U.S. you hold a copyright to it at the moment you put the characters onto disk. In the case of work-for-hire (i.e. you are employed as a software author by your company), the company holds that copyright. No one else has permission to use, copy or distribute the software without the express permission of the copyright owner. Licenses are the mechanism used to bestow rights upon other users (or, in the case of Open Source Software, potentially other developers) of the software.

Switch gears a bit: other companies (vendors) providing interesting systems (those that you or your company are interested in using) also provide information on how to interoperate with their systems and libraries. When using the C family of languages, this information is provided in a machine-readable format known as a "header" - the header file is source code that describes the procedures made available inside the vendor's code libraries. You include this header in your own project so the compiler can validate that you're calling the library code correctly. They've given you a binary library and not the source to the library to help in protecting their rights to their original code.

Now, after years of offering a particular product on the market, a vendor (Vendor A) decides to discontinue offering this particular product regardless of the fact there are numerous client who still use this product and are willing to continue to pay for support. They are not willing, for whatever reasons, to completely overhaul their own systems and incur the immense expense in changing to this vendor's completely new and different product.

Company B steps in offering an interoperable replacement to that old system that's been discontinued by Vendor A. Company B created a completely legal replacement for this system because they did not use Vendor A's source code. They created a "clean room" implementation of the system. As far as the client's systems are concerned, the interfaces into Company B's solution look exactly like Vendor A's system, to the clients network, employees and customers carry on with business as usual.

Courts have ruled that creating systems for such interoperability is legal and necessary. Without such recognition, vendors have the opportunity to lock their customers into the vendor's products. Interoperability is defined by interfaces to systems and libraries. The interface into a library is an Application Programming Interface, or API. The API has pretty much been declared to not be of the expressive type required to obtain copyright protection. If API's become completely protectable by copyright (and thus require a license to use), companies can then limit the ability for others to provide interoperable systems thus limiting competition. In this case, the legal freedom of developers to create tools and apps around an existing system is severely limited and perhaps even eliminated, regardless of the fact that these developers didn't use any code from the vendor in the process.

kunai• 13 years ago

The future of Java went downhill as soon as Oracle bought Sun.

I miss Sun. Dearly. They were perhaps the only major IT company with a true heart.

And now there's none left. Google? Hell no.

Developer Freedom At Stake As Oracle Clings To Java API Copyrights

Related Stories