Oracle Tells Supreme Court Google Copyright Breach Knocked It Out Of Smartphone Market (crn.com)
Joseph Tsidulko, writing for CRN: Oracle asked the U.S. Supreme Court on Wednesday to not review an appellate court's decision finding Google violated Oracle's copyright of the Java platform when building the Android mobile operating system. In that opposition brief, Oracle's attorneys said Google's copyright violation shut Oracle, the Java platform owner, out of the emerging smartphone market, causing incalculable harm to its business. The complex case pitting two Silicon Valley giants against each other has raged on since 2010, and already saw many twists in turns before a circuit court last year reversed a jury decision in favor of Oracle. That prompted Google's appeal to the nation's highest court. Oracle notes Google had previously asked for a writ of certiorari -- the legal term for review by the high court -- in 2015 without success in an earlier phase of the case, and the company argues nothing has changed in the time since.
Oracle believes Google destroyed its hopes of competing as a smartphone platform developer with the Java platform, which enables development and execution of software written in Java, including through APIs that access a vast software library. The lawsuit alleged Google copied those APIs without a proper license. Java was developed at Sun Microsystems, which Oracle acquired in 2010. "Google's theory is that, having invested all those resources to create a program popular with platform developers and app programmers alike, Oracle should be required to let a competitor copy its code so that it can coopt the fan base to create its own best-selling sequel," Oracle's brief states.
Oracle believes Google destroyed its hopes of competing as a smartphone platform developer with the Java platform, which enables development and execution of software written in Java, including through APIs that access a vast software library. The lawsuit alleged Google copied those APIs without a proper license. Java was developed at Sun Microsystems, which Oracle acquired in 2010. "Google's theory is that, having invested all those resources to create a program popular with platform developers and app programmers alike, Oracle should be required to let a competitor copy its code so that it can coopt the fan base to create its own best-selling sequel," Oracle's brief states.
Who do I root for?
Hopefully this will be a very long, messy, and expensive legal battle for both companies.
#DeleteChrome
I'm fascinated to hear what products Oracle had in the works that Google wrecked by re-using Java library headers.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Yeah, I'm a bit confused here. I don't recall Oracle or Sun ever trying to break into the smartphone market.
And frankly knowing Oracle I'm so incredibly glad they didn't.
Precedence... Google might look to a certain OS MS-DOS that copied the API of CP/M.
Of course, I'd be remiss if I didn't admit that I prefer to be abused by Google to being abused by Oracle. So I might be biased.
I'd like a list of the # of entity's that have actually paid Oracle a license fee for a single Java API. I betting the number approaches ZERO.
A smartphone developed by Oracle?
I've been fortunate enough never to have crossed paths with Oracle's infamous licensing terms, but I could picture it now:
Every time you used your phone for any purpose whatsoever, you'd have to pay a fee to Oracle.
So rise up, all ye lost ones, as one, we'll claw the clouds.
Well while I don't agree with Orcacle's theory that interfaces can be subject to copyright. I would agree with the assessment Google by creating their own JVM essentially drove Oracle out of the mobile market place. J2ME Was pretty widely used in what we think of as the pre-smartphone era.
I don't see any reason why it would not have become the defacto application platform going forward, except for entrants like Google with resources enough to implement their own JVA not wanting to pay Oracle for theirs.
Remember when blamer said "developers..developers..developers.." same thing applies here its not like Google chose Java as their implementation language for Android because the syntax is so sexy and everyone love it. They picked it because a lot of people know it. J2ME would have probably continued as a force without Davlik and just got some sexy new interface libraries to bring all the existing mobile phone developers and desktop java developers over.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
That's not how it works.
You hire lawyers and politicians to make it legally impossible for people to go with a competing product, then you launch your own inferior product and wait for the money to roll in.
THAT's how it works.
Competing on actual merit is so last century.
Oracle believes Google destroyed its hopes of competing as a smartphone platform developer with the Java platform,
The only ones who destroyed their hopes of making a phone people would buy was Oracle. They have done a great job of getting their name out there in the market and setting expectations. The problem of course is that their name and those expectations are not well regarded. So if I were in the market for a phone and went into the store and saw an Oracle one I would definitely pass it up. But then again I was never of the normal, so maybe its just me.
Java was the most popular language for mobile apps before Android came along. Nokia's Symbian OS in particular had many Java based apps, and the industry could see where things were going: apps that run on phones, TVs and laptops, basically everywhere.
Symbian was crap though and apps were generally terrible. Android quickly took over, and how Android apps so in fact run on phones, TVs and laptops.
Oracle is arguing that they could have been a major player if Android hasn't used their API, but in reality Java failed because it and the Symbian OS and the non-touch phones it ran on were all shit.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
So it's devolved to the level where Oracle is little more than a gigantic patent troll so Larry can have a bigger sailboat. F#ck them all, Larry, Oracle and that spyware company, Google..
That would be glorious - Oracle phone running Java Applet with MS Clippy.
Oracle was in the smartphone market?!? When the heck was that?
J2ME's UI options and system services were terrible for mobile.
Android, for all its warts, was substantially better. Java just happened to be a decent language for the time that could be hooked into the Android stack.
If it had been Swift or Python or Ruby it still would have pantsed any J2ME phone offering. Java isn't all that special. Look at iPhone - lots of people learned Objective-C just to use its mobile stack and in that case Apple itself showed how non-optimal a language that is by developing Swift.
Oracle is attempting to mislead the Court.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Oracle's argument is: I couldn't go to the party because Google was already there wearing the dress I wanted to wear?
Tough luck. The courts are not there to make sure one company's profits are protected at all cost. Even if it is true that Google drove them out of the mobile market, it still doesn't mean APIs can be copyrighted. The case in court is not about whether Google hurt Oracle's feelings or not.
"Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
Apple did not make native apps a choice for iphone until after the product was released. The chose obj-c because that is was OSX was being built with and that is what all the smart people they had pulled in from Next knew. So the choice of obj-c was very much one about developers..developers..developers it just so happened to be internal developers when that call got made.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
Well, "most popular language for mobile apps" is misleading. C was the most popular language for mobile code.
But C didn't have sandboxing capabilities, etc. Fault isolation and data protection in native code relies on a memory protection unit, which was too complex/expensive to be included in dumb phone processors.
So downloadable "apps" mostly used Java which had some inherent security features based in a mandatory type-safety system.
But "smartphones" have always had better hardware, and in particular they've had MPUs, so there was no reason to use (slow, bloated) Java except for portability. And in the early days of smartphones there were only 3 or 4 processor architectures in use, and any OS that had more than one had enough smarts built into the app deployment systems (for example, ActiveSync for WinCE) to pick the right binary for the phone.
So Java never had a foothold on honest-to-God smartphones before Google introduced Dalvik and Android -- only on feature phones. So you may be able to make the statement true by adding enough qualifiers -- "the most popular language for MMS-downloadable applets on feature phones" -- but that was a doomed niche.
Oh, I'm sure they'll figure out a "calculation" for the judgement.
Did I say it was? Oracle is not entitled to the mobile market. Like you I disagree with the premise that interfaces can be subject to copyright. If the court however finds otherwise; than damages will have to be figured. If we are forced to presume by the courts finding that interfaces can be copyright; than all I am saying is Oracles argument that Google cost them the mobile space probably does follow, and Google will in that instance be required to pay dearly.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
Java was the most popular language for mobile apps before Android came along.
It still is. Android is an operating system not a programming language.
Oracle is arguing that they could have been a major player if Android hasn't used their API.
The case in court is not about which player is major or minor or how much profit Oracle would have made if Android did not exist. The case is about whether APIs can be copyrighted. If you are allowed to copyright APIs then you are also allowed to copyright a file format.
If they had a patent on it, it would be a different discussion but I don't see how it can be copyrighted.
"Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
I don't know Symbian native development but I work with developers who say it was pretty decent at the time.
However, in my experience J2ME on phones was a horrible developer experience. The implementations were terrible, incompatible, incomplete, hard to get decent documentation for, even harder to get developer support for, easily crashed some phones (hey Siemens) etc. Write once, work nowhere. Nokias Symbian phones were the most pleasant ones I got to develop J2ME apps for. Yeah, it was still crap.
Oracle is shit, and their java is a piece of garbage.
They want my sympathy - they need to create a product I'd want to use.
We should make Google a Thank You card for keeping Oracle out of the Smartphone market.
Make America grate again!
You have it reversed. With the new standard tht APIs are copyrighted, it will kill open source software.
Oracle has caused a lot of harm to java with this litigation, with its bad handling of security issues and its general bad governance. The fact that Google has made so much effort to use java in android is a testimony to the qualities of this language.
When Google came on board with Dalvick, Sun was having a grand time putting JAVA in the browser and on the server. Those wanting to put it into embedded devices, it's original intent, were ignored by Sun Microsystems. As HP about that since they wanted to license JAVA for use in their printers but Sun would not address their requests for licensing. HP had to do a clean-room implementation which they called Chai or something like that( as in the tea ). No doubt there were many others since we all know HP is no small printer manufacturer and landing them would have been a large deal.
But somehow we are to expect, or the judges are, that it was all Google's fault? Java on mobile phones, back when phones were not very smart, was a mess with many different layers of API's to follow. I forget what they called that mobile version of JAVA but each phone vendor had different application stores and different application requirements.
Apple showed that the market for downloading applications on mobile devices was viable again( remember Palm did it years before ) and Google just followed their lead. Had the phone vendors considered their Sun JAVA mobile API's sufficient they could have competed but they were stuck with what Sun provided and it was not really so good for the rich smartphone OS which was becoming the norm.
Oracle purchased Sun thinking they'd leverage JAVA everywhere but Sun left the mobile market and focused on the server side and browser...
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
No seriously, that might as well be the excuse from Oracle. They are pretty much saying "since Google used this language/API that we wanted to patent troll AFTER they forked it and already had Android all rolling, we pretty much can't be on that market, because the way we WOULD be on that market was to do nothing more than demand royalties from Google by using this technology that we simply purchased without actually thinking through that it was OPEN SOURCE BEFORE".
I could say this is funny. But it is actually way more than that.
We all remember those beautiful sleek end-user friendly and exciting products from Oracle, before evil Google came along and destroyed de poor liddle Oracle and their beautiful consumer products lineup.
Sooo mean, sooo sad.
We suffer more in our imagination than in reality. - Seneca
I think it was just about the money. Fame and glory they could make up later, how they saved java from the evil hands of Google. All praise be Oracle!
and taking "back" control of the mobile platform.
Maybe it would have had to rebrand it. e.g. Orafix, Mava (mobile java),..., what have you.
Nothing stopped Oracle from pulling a CyanogenMod move, but backed by Oracle's money.
Nothing except lack of willpower, imagination, and skill.
Where are we going and why are we in a handbasket?
I'd be more inclined to buy a phone branded Etch-A-Sketch than Oracle.
Funny thing is, J2ME was pretty big business pre-iOS and Android. Probably had the largest market share of any mobile platform, at least up there with native Symbian apps. Oracle did basically nothing with it, as they bought Sun primarily for enterprise Java and server hardware. Then, when Android blew up, Oracle finally realized they could make some money off of a mobile Java platform, but it was too late. They had done nothing with J2ME and it was so far behind anything else as a platform the only way they could monetize was to sue.
My Other Computer Is A Data General Nova III.
Oracle had such overwhelming success with SPARC chips, how about a SPARC T4 in a smartphone? It could also act as a handwarmer. Let's see Apple top that!
The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
No one stops Oracle to take Android (or would they need to pay a license fee?) and sell their own Android device.
However if they put their Oracle database on it, I would ski :P
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
With the new standard tht APIs are copyrighted
Minor correction, can be copyrighted. Not every API that comes into existence automatically becomes copyrighted unless the author says so and even then if they only enforce it.
I don't agree with the idea that APIs can be copyrighted, but, what I do and don't agree to means nothing in the legal system. That said, I don't see this as something that kills open source software. Not giving something a legal definition leaves it in murky waters. With APIs being something that can be copyrighted, it's easy for projects to require the APIs be copyleft/GPL/BSD/etc. Copyrighted APIs become an issue for people who've done projects with APIs with less than clear legal language, which was the case since APIs were pretty much just assumed to public domain/just how things work. And trust me I would love to see APIs having that legal distinction, but they don't and you work with the reality your handed.
A lot of the modern APIs in major use today are already open sourced and apply either a copyleft/GPL/BSD requirement to the licensing of the API. Hell, even Java today is GPL API via the OpenJDK. And OpenJDK's special exception that was irrevocably granted by Sun before they gave up Java, is how Google to this day keeps Android alive. Google was once upon a time not down with going GPL and wanted to use Apache License. Which you cannot convert simply relicense a GPL project to Apache License project, which was the entire argument that Oracle made in court against Google.
I don't like the notion of copyrighted APIs anymore than the next person, but I do see that APIs being copyrighted isn't the death knell for future projects. But I totally see it as a submarine issue for projects from the past. Much like how patent submarines were once used before a change in the patent law.
And I say that as an atheist. Oracle is the proverbial Evil Inc. that only cares about fucking its customers over.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Too many companies that made abysmally bad strategic IT decisions and not cannot get rid of Oracles crap. My students tell me they expect Java to be dead within a few years (due to the upcoming fees by Oracle), but it will be decades until all legacy stuff is gone.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Slowlaris on a phone? Could the ideas get any worse?
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
You left out "Engage in regulatory capture to lock out competition".
I thought I covered that with hiring politicians.
Minor correction, can be copyrighted. Not every API that comes into existence automatically becomes copyrighted unless the author says so and even then if they only enforce it.
Your correction is incorrect, at least in the United States. Creative works are automatically protected by copyright from the time they are created; no additional action by the author is necessary. Unlike trademarks, copyright (as well as patent) protection is not lost for failure to actively defend it.
Oracle's crap software and their high pressure sales goons put them out of business.
Corporatism != Free Market
They took the 95 percent completed Harmony 5/6 libraries, reimplemented by the Apache Foundation and hundreds of paid and volunteer developers, and finished the remaining 5 percent or so after Sun open sourced Java. So this is even more questionable than Oracle is making it out because it was already 'second source software' before Scroogle ever got ahold of it.
The fact that they made a better hammer than the original hammer-maker is entirely down to Sun and Oracle's lack of vision. Or google's for that matter, since Android was bought, not developed in-house.
Oracle is attempting to mislead the Court.
No shit Sherlock ! Understatement of the year. Anybody with 10 minutes of reading on the subject can see that, so why haven't they been thrown out yet, with prejudice ?
Non-Linux Penguins ?
Suing Google for using Java for Android pretty much guarantees the death of Java!
I've abandoned my search for truth; now I'm just looking for some useful delusions.
There are many, many, people who have successfully done so. Your disagreement with their choice does not make it any less valid. You legally get copyright, but you are free to license it any way that you want, including free for everyone with no strings attached.
I forget what they called that mobile version of JAVA
I believe it was, oddly enough, Java ME (Mobile Edition)
General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
Android is an operating system not a programming language.
And it might actually be just a Linux distro.
I thought the problem was that it was slow on x86, but worked fine on RISC platforms? Phones are mostly ARM.
That wouldn't be the problem. The problem would be, where would apps come from, and where would security come from?
Careful. You may be committing the common and understandable error of thinking that J2ME = J2ME CLDC. There was a less stripped down framework called CDC which had a couple of profiles with UI based on AWT. IBM had an implementation for PocketPC. It would have been a suitable basis for something which went beyond feature phones if a company with the right vision had taken it on in about 2003.
They did the same damned thing to my company. I tell you, if it weren't for them and their Java rip-off, everybody would be making cell phones.
Do you have ESP?
Apple showed that the market for downloading applications on mobile devices was viable again
Quite the opposite. Apple didn't want to ship a SDK and have 3rd party developers write apps for the iPhone. They pushed for web apps only (and their own native ones of course). They did end up giving in and shipping a SDK. So it wasn't Apple showing that the market existed, the market was so overwhelming that Apple had to join in even as it held it's ears and claimed it wasn't important.
There were plenty of app stores and app platforms that pre-dated the iPhone that were doing just fine. Apple reluctantly joined in too.
Java on mobile phones, back when phones were not very smart, was a mess with many different layers of API's to follow. I forget what they called that mobile version of JAVA but each phone vendor had different application stores and different application requirements. Apple showed that the market for downloading applications on mobile devices was viable again( remember Palm did it years before ) and Google just followed their lead. Had the phone vendors considered their Sun JAVA mobile API's sufficient they could have competed but they were stuck with what Sun provided and it was not really so good for the rich smartphone OS which was becoming the norm.
J2ME (Java 2 Mobile/Micro Edition) was their primary mobile platform, and it was successfully deployed in may places. BlackBerry OS was built upon JME itself (before Java 1.0 got to Java 1.2 aka "Java 2").
Along those lines of Oracle's current claims, the future success of Java as a mobile platform/ecosystem was somehow stunted by Android OS... and not the continued failures and feature deficits of the underlying Java ME platform and their existing commercial mobile OSes. If I recall, the Java ME platform had such a lousy stench to it that Apple quickly dismissed its usage in creating iOS (so it was in the running but tripped on its own insufficiencies).
I agree, LoB, that Oracle's purchase of Sun (and thus Java) was not primarily for mobile ambitions because Sun quick the mobile market before talks began! Sun needed an exit strategy and Oracle came with open arms.
Your correction is incorrect, at least in the United States
You are correct on this. That is Trademark that requires legal defense and Copyright requires overt act to release to public domain.
That said, in the United States, I believe the majority of what I said still applies. Modern APIs are more explicit about the licensing requirements for the API and GPL et al convey an open agreement for the APIs. Additionally, Copyright in the US permits fair use as well. While I wouldn't want to attempt playing within that domain, new projects convey fair derivative use of APIs be it in explicit terms for non-standard licenses or in some of the more commons ones we've come to know. Additionally, I think people are more aware of APIs usage today than they once were.
Again, the biggest problem I see with copyrighted APIs is prior projects that implemented "fuzzy" in legal terms APIs. So that being said, I don't see copyrighted APIs as a hindrance for future open source projects. However, I will reaffirm that my preference here is APIs not being a copyrighted thing.
I forget what they called that mobile version of JAVA
I believe it was, oddly enough, Java ME (Mobile Edition)
It was Micro Edition (embedded) before it picked up the temporary marketing rebrand of Mobile Edition.
Solaris is pretty slow on anything. And it has a really bad network stack and that is after it was cleaned up.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Doesn't Oracle already have the old BSD network stack, though?
Python!? ROFLMAO. What a steaming pile of holy shit.
If Oracle had the vision at the time, Google using the same platform for app development would have helped them significantly.
Except Google started using Java when it was still owned by Sun Microsystems.
Oracle is still around because it has lots of money. Money from entrenching itself in a lot of large companies.
It's been a tough week, and I needed this. An Oracle phone. A successful Oracle phone.
Thanks guys. ^_^
A government is a body of people notably ungoverned - AC
What are you talking about?
All Google did was build their own platform using the Java language and API. They didn't take or change any code.
Not Oracle, but Sun has a lot of history in closely related spaces. The original Java platform (back when Java was called Green) was the 7*, a handheld computer that ran a modified Solaris that supported execute in place and ran happily with a 32-bit SPARC and 1MB of RAM. The vast majority of pre-iPhone smartphones and featurephones included J2ME, which (unlike J2SE) required a license fee from each phone maker.
This is the main reason that Sun was unhappy with Android. They'd been receiving royalties from pretty much every phone to be able to use Java and then suddenly Google came along with a Java implementation that didn't require anyone to pay Sun. Worse, as with Microsoft's J++, it wasn't a fully conformant implementation of Java - it did both subsetting and supersetting, so arbitrary Java code doesn't work on Android and arbitrary Android Java code doesn't work on other JVMs.
I am TheRaven on Soylent News
cheap phone and it felt that way. My provider loaded a breakout clone on it. Really simple, just ball, 10x10 colored blocks and a paddle. Kind of thing that make the Atari 2600 a household name in the late 70s/early 80s.
It was dog slow. Unplayably so. I mean, I know it's a cheap phone and all, but come-on. It's a clone of Atari breakout.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
I would agree with the assessment Google by creating their own JVM essentially drove Oracle out of the mobile market place.
That's utter horse shit. Google adopting Java was the one thing that kept Java alive and growing. Java was well adopted on the server side, but that was it.
The JVM had a half ass implementation on dumb flip phone mobile devices before the smartphone market took off.
If anything it was Oracle's idiotic move to sue Google for using Java that killed Java as an option on other platforms. Why would other platforms use Java if Oracle is just going to turn around and file a multi-million dollar lawsuit. Oracle shot themselves and Java in their own ass.
Sun was in financial trouble.
Oracle had to buy it out to stop their competition acquiring Java. All their corporate products are built using it or embed it.
Having to call their flagship product "Oracle Database, powered by Microsoft Java" would be bad for them.
for instance, how's it going to work putting an antenna on a SunServer and carrying it on the bus to talk to your significant other.
if this is supposed to be a new economy, how come they still want my old fashioned money?
eBay would just do an Amazon and migrate away from Oracle.
Nah, they'd let you use it as much as you want, but every year they'd come in an audit your usage and send you an invoice.
Their database licensing model is to let their customer install it on as many machines as they want, when ever they want, without asking for permission. They then send an invoice based on how many cpu cores you're running it on.
Kind of like a loan shark or a drug dealer.
Are you implying that SWING worked before Android?
Back when MS was forced to ship a copy of Sun Java, I thought they should retaliate by also shipping a copy of SWING and using it to render Sun's logo at startup.
John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
Oracle's database is good, not worth the money, but a good solid product.
Everything else they make/sell is _useless_ shit that makes SAP look good.
John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
I believe they purchased Sun because they used Java for interacting with their Database, and the last thing they wanted was someone buying Sun and hitting them as they hit their customers. Once they had it they tried to do exactly what they thought others would have done had they got the asset. Had Sun been healthy I don't see Oracle being interested in it at all.
Almost right. The SCOTUS, I think, just ruled that copyrights are not enforceable until the until the Gov't paperwork is completed. The long standing practice of assuming that everything created is copyrighted and immediately enforceable, has been shot to hell.
Can you cite to the Supreme Court case? The Berne Convention says that works are automatically protected by copyright.
The US government disagrees with you:
Federal Regulations as they pertain to software (from https://www.copyright.gov/title37/201/37cfr201-26.html):
Title 37 Part 201.26:
(b)(3) Public domain computer software means software which has been publicly distributed with an explicit disclaimer of copyright protection by the copyright owner.
That means that you can in fact explicitly place something in the public domain. Once you do that, you can not go back on those people who have used that version. Now there's nothing stopping you from distributing a new version under a different license, but that's not the same as reversing the decision on the original.
What OP probably meant to say is that copyrights do not need to be enforced. The owner of an API copyright can simply state up-front that they will not be enforcing the copyright, and everyone can use the API freely without restriction. Which will cause people and companies to gravitate towards these open APIs instead of closed ones like Oracle is trying to make JAVA into. And eventually, the only APIs used between companies will be open ones whose copyright is not enforced.
Raising the question of what the hell was the whole point of making APIs copyrightable? When the only form of API which can self-perpetuate in the market is the kind which foregoes the protections offered by copyright?
Let's all feed Larry.
When all you have is a hammer, every problem starts to look like a thumb.
Oracle has the power to publicly destroy almost everyone as well. Oracle has destroyed a lot of open source projects, and if they win the right to prevent anyone from using an API means that this would destroy even more open source.
And it's highly suspect in the first place that an API actually can be copyrighted. That's like copyrighting a table of contents. At the very least, fair use implies you can freely use an API.
I sometimes pass this building in Silicon Valley that has a banner in the window saying "We Love APIs". Which I have thought every time that the building must be full of morons. An API is like saying "I'll meet you at 2:30 in conference room B".
And it's highly suspect in the first place that an API actually can be copyrighted. That's like copyrighting a table of contents.
Just to clarify, I don't disagree with this point. I only wanted to correct the mistaken statement that additional action is required by an author to get copyright protection for a work that is eligible for protection.
Clarification: "Before, copyrights were mostly limited to implementation."
Table-ized A.I.
Where's PJ to explain this to us when we need her?
That's like copyrighting a table of contents.
It really isn't like that at all. An API, its design, data model, guarantees and so-on, is actually the hardest thing to design. Once designed, the implementation is relatively straightforwards. The main different between Android, and iOS, for instance, is that Android's APIs are horrible, and iOS's are really nice to use. This is an API design issue, it's nothing whatever to do with the underlying implementation.
Or look elsewhere, at a less divisive example. Microsoft's WIN32 API is terrible. Everything is a handle, one ends up having to cast things all over the place. The message queue takes only a couple of integers as payload. There's no support for basic things, like JPEGs. And hands up anybody that's ever tried to use their DirectShow media APIs. Oh, that's right, you can't. You've long ago chewed your own arms off in frustration.
That's poor API design. It's massively important, and very hard to get right. For the record, I don't believe that Java's APIs are particularly nice. An likening an API to a "table of contents" is disingenuous at best.
I only wanted to correct the mistaken statement that additional action is required by an author to get copyright protection for a work that is eligible for protection.
To which I am happy to have been corrected, might I add.
There were plenty of app stores and app platforms that pre-dated the iPhone that were doing just fine.
Well, I suppose 'doing just fine' is a statement that's opening to interpretation, but I can't think of any that fit my own personal definition of that term.
Whatever they're on is amazing!
To be precise, copyrights are vested upon creation, but lawsuits to enforce the copyright may not be brought until the US Copyright Office issues a registration for the copyright or denies it (in which case the suit will also have to argue that the denial was wrong).
The case is Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, and the link is to the unanimous opinion of the Court.
-- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
Correction, the link is https://www.supremecourt.gov/opinions/18pdf/17-571_e29f.pdf and whoever runs the site now is a son of a bitch, who hasnâ(TM)t programmed it to figure out what to do with smart quotes from mobile devices and who doesnâ(TM)t offer a chance to preview the post from the mobile interface. Hopefully this works better.
-- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
However, it is possible to have an API - or anything else - that is uncopyrightable if it is not sufficiently creative, or if the merger or scenes-a-faire doctrine kick in.
-- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
Interesting. Thanks for answering that.
Thanks for clarifying that. Yes, everything I said certainly only applies to works that are eligible for copyright protection in the first place.
If Oracle wasn't seriously planning to make phones, their argument collapses. And they'd have to show it would have had a chance in hell of selling. Microsoft couldn't survive in the phone market, why would Oracle?
Those wanting to put it into embedded devices, it's original intent, were ignored by Sun Microsystems.
This is patently (lol) untrue. I recall seeing Java implementations running on smart cards in 15k of RAM back around the 2k time frame.
Licensing was likely a serious issue, but there was Java in embedded spaces, so it was not "ignored". There was some other reason... likely had to do with money.
"Someone needs to talk to the tree of liberty about its ghoulish drinking problem." by ohnocitizen
I agree: the amount of money they could have lost trying to sell an Oracle Smart Phone is incalculable
just a ghost in the machine.
Google is being blatantly honest that they're censoring for China.
If it was anyone else they probably would have done it quietly and we'd never have found out about it.
In this case I see that Google is doing the censorship under protest because otherwise the powers that be in Beijing wouldn't let Google operate at all, so they're doing it while giving the authorities the biggest middle finger they can without putting themselves in jeopardy.
And to be quite blunt I would rather have Google give openly censored results than have someone else filling the void who would not only hide that they're censoring, but likely trace anyone even searching for it and hand the results over to the authorities for persecution.