Taking too long? Close loading screen.
Connect with us

Tech

Oracle and Google’s Supreme Court showdown was a battle of metaphors

Published

on

Google v. Oracle, a decade-long war over the future of software, neared its end in the Supreme Court this week as a battle of metaphors. Over the course of two hours, justices and attorneys compared Java — the coding language that Oracle acquired in 2010 — to a restaurant menu, a hit song, a football team, an accounting system, the instructions for finding a blend of spices in a grocery store, a safecracking manual, and the QWERTY keyboard layout.

“Prediction: The side that wins the metaphor battle will win the case,” tweeted University of Oklahoma College of Law professor Sarah Burstein.

The reliance on familiar analogies wasn’t necessarily surprising. Google v. Oracle covers a complex question: what elements of computer code can be copyrighted, and if that code is covered by copyright, when it’s still legal to use pieces of it under fair use. The argument dates back a decade to when Google reverse-engineered Java while building its Android platform. In the process, it copied the “structure, sequence, and organization” of some Java application programming interface (API) packages, which enable basic computing actions. Oracle sued, and after multiple trials and a coronavirus-related delay, the Supreme Court heard the argument this week.

After a morning of long-delayed oral arguments on Wednesday, both sides declared a win. Google head of global affairs Kent Walker said the court “confirmed the importance” of the legal rights protecting software interoperability, while Oracle general counsel Dorian Daley declared that the court would “agree with us that all software is covered by copyright.” Tiffany Li, a fellow at Yale Law School’s Information Society Project, cautioned against reading too much into the proceedings. “It’s difficult to guess how a case will turn out based on the arguments,” she tells The Verge. “But it’s interesting because you get a little bit of perspective on what the justices might be particularly interested in.”

Constructing metaphors for Java’s API let justices interrogate whether the code was a basic tool that Google was using because it was the most efficient option, or whether it was a creative original work that Google was unfairly exploiting to avoid doing its own work. “Someone could argue that if a team takes your best players, a football team, that the only way that those players could actually perform at a high level is if you give that team your playbook. I don’t think anybody would say that is right,” argued Justice Clarence Thomas — loosely equating Java code libraries with the football players.

Google attorney Thomas Goldstein argued that the football analogy was missing the point — Oracle wasn’t trying to keep “fans” for its sports team, just “prisoners” for its Java SE platform. “Why would Congress want a rule that says: ‘okay, these developers are extremely familiar with these commands. They’re used to write creative computer programs. Let’s just make it as inefficient as possible for them?’” he said. “The only upshot of Oracle’s rule that it wants you to adopt is to make computer programming incredibly inefficient so that we have fewer creative computer programs.”

A recurring comparison to keyboards was more sympathetic to Google. “You didn’t have to have a QWERTY keyboard on typewriters at the beginning,” just like Google could have built code that didn’t reference Java, said Justice Stephen Breyer while questioning Oracle’s attorney. “But my God, if you let somebody have a copyright on that now, they would control all typewriters, which really has nothing to do with copyright.”

The justices didn’t necessarily seem convinced that Oracle’s API wasn’t protected by copyright, but they seemed potentially sympathetic to arguments that Google applied the code transformatively in a way that counts as fair use. “My sense is that Google is more likely to win on fair use than on copyrightability,” says Berkeley Center for Law & Technology co-director Pamela Samuelson.

Google v. Oracle could have massive implications for software developers. A group of 83 computer scientists, including many early software design luminaries, filed a brief arguing that a Supreme Court win for Oracle would discourage developers from building on existing code to make something better or from designing interoperable software. “Software will become harder to use because switching to a competing service will require users to learn an unfamiliar interface,” they warned. “Rather than switch to more innovative software, users will remain locked in to outdated systems.”

But the mess of metaphors left doubts about how much the justices grasped the difference between an API — which is a key piece of operational code that lets different pieces of software work together — and the code of a discrete app. “What stood out to me was that I am not sure if Google’s attorney made it really clear what an API is. And that’s not ideal,” says Li.

And unfortunately, most of the hearing’s analogies don’t map very easily to actual copyright law. A QWERTY keyboard would be covered by patents, not copyright, for instance — and patent infringement charges were dropped from the case years ago. (As Oracle’s attorney Joshua Rosenkranz pointed out, “there was never anything expressive in QWERTY. … It was purely mechanical.”) Comparisons like the football playbook get at general notions of fairness, but that’s not necessarily what this case should hinge on. There are also even more legal questions that the court could rule around, like whether an earlier jury verdict should have been thrown out.

On the bright side, Li was at least somewhat heartened by the amount of time given to questions about the future of computing, not just the logic of coding. “Many justices are asking, what does this mean for the software industry?” she says. “And it’s interesting because people who actually work in tech, I think most of them realize that there is just so much use of free and open source code that’s just foundational in so much software. So limiting the ability for people to use this kind of thing or to create their own code that might copy or borrow from or refer to existing code — that would severely limit the industry.”

Source

Continue Reading
Advertisement
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Tech

You can now buy Vizio’s rotating Atmos soundbar

Published

on

Vizio’s Elevate soundbar has finally hit shelves. You can buy it today for $999.99. The 48-inch soundbar supports Dolby Atmos and DTS:X. The soundbar houses 18 speakers and comes with a wireless eight-inch subwoofer. The cool thing is that some of the speakers rotate — they face upward while you’re playing Dolby Atmos content and point forward for standard audio.

I spoke to Vizio CEO William Wang about the Elevate earlier this year. He said the soundbar is intended to hook non-enthusiast customers on Dolby Atmos by showing them, visually, the difference between the two tiers of audio. He also noted that while the Elevate is asking a steep price, he expects the rotating speakers to appear in lower-cost devices down the road. The Elevate is being positioned as a good companion purchase for Vizio’s first 4K OLED TV, which is also now available.

Currently, you can order the Elevate at Best Buy and Walmart. Vizio says it’s coming to Amazon and Sam’s Club, too, but those don’t appear to have active links yet.

Source

Continue Reading

Tech

Don’t Eat Deli Meat if You’re Pregnant or Old, CDC Says

Published

on

slices of salami on bread, surrounded by pretty food things

Photo: photocrew1 (Shutterstock)

There’s an outbreak of listeriosis linked to deli meat, the CDC says. The exact source has not been tracked down, but they say if you are pregnant, over 65, or have a weakened immune system, to not eat deli meat or take extra precautions.

Advertisement

Listeria bacteria can live at refrigerator temperatures, but are killed by heat. That’s why they turn up in deli meats (including Italian style processed meats like salami) and soft cheeses made with unpasteurized milk. If you’ve ever been told not to eat brie while you were pregnant, this is why—although most soft cheeses in U.S. supermarkets aren’t made with raw milk. In the past few years, Listeria outbreaks have also been linked to lettuce and other produce.

If you don’t fall into those risk groups, listeriosis is not a serious illness. But if you are pregnant when you get it, it could cause miscarriage, stillbirth, or death of your newborn. It can also be serious for people who are elderly or have a weakened immune system.

Advertisement

The CDC says it knows of 10 recent cases in which people were hospitalized, and one died. Here’s what they say about the source:

  • Ill people have reported eating Italian-style meats, such as salami, mortadella, and prosciutto.
  • People have reported purchasing both prepackaged deli meats and meats sliced at deli counters. The investigation is ongoing to determine if there is a specific type of deli meat or common supplier linked to illness.

If you are in one of the higher risk categories (pregnant, older, or with a weakened immune system) the CDC recommends either avoiding deli meats or making sure they are heated just before serving until they are steaming hot. (That’s an internal temperature of 165 Fahrenheit, if you’re able to get a thermometer probe into your salami.)

You should also wash your hands after handling deli meats, clean any surfaces that deli meats or their juices have been in contact with (such as your refrigerator shelves) and make sure you’re not keeping deli meats in the fridge too long. Meat you buy from a deli counter is usually good in the fridge for five days; factory sealed packages are good for two weeks.

Advertisement

Source

Continue Reading

Tech

See Who’s Mooching Off Your Netflix Account by Checking Its Recent Access

Published

on

A screenshot of the Netflix

Screenshot: Joel Cunningham

Depending on how much you pay for your plan, your Netflix account can only be used by so many people at once. Exes, old roommates, or thoughtless siblings—anyone you’ve unwisely trusted with your password—might be mooching off the account you pay good money for, but it’s not too difficult to find out if they are.

Advertisement

A simple trip to your Netflix account settings will allow you to discover the IP addresses and locations of whoever has been accessing your account. Here’s how to find it:

  1. Head to the Netflix home page in your browser and sign in.
  2. In the upper right-hand corner you’ll see your account symbol. Mouse over it, then click “Account.”
  3. Scroll down and click the “Recent device streaming activity” link.
  4. Then click the “See recent account access” link.

Advertisement

You’ll see the IP address, location and type of device that has been watching Netflix with your account, as well as when. You’ll probably be able to deduce who has been using your account from there. Once you know who is mooching, you can ask them to get their own account and stop filling your queue with bad movies, or you can just return to the Account page, choose “Sign out of all devices” and then change your password in your account settings and shut them out for good.

Netflix also allows you to download some content to your device(s), but how many are allowed to do so will once again vary based on the details of your monthly plan. From your Account page, you can also select “Manage download devices” to remove any that are unauthorized; this will remove content downloaded to those devices and free you up to offload content on your own phone or tablet.

This post was originally published in 2016 and updated on October 27, 2020 with more complete, up-to-date instructions and screenshots.

Source

Continue Reading

Trending