Defenders dispute Java-copying claim against Google

By Geoff Duncan January 24, 2011

Image used with permission by copyright holder

Last week, intellectual property expert Florian Mueller caused a stir by distributing a 46-page analysis in which he examined the source code files for Google’s Android operating system and claimed to have found numerous instances where Google copied Oracle’s Java code outright, or de-compiled it using software tools. The assertions seemed to back up Oracle’s infringement suit against Google: that suit, if successful, could lead to Oracle collecting a payment for every Android device sold.

However, ZDnet’s Ed Burnette—an actual software developer—disputes Mueller’s conclusions: he downloaded the same files that Mueller examined and concludes they don’t bolster Oracle’s case against Google. Burnette’s analysis is that none of the files in question are actually shipped as part of the Android operating system, and at most contain the equivalent of clerical errors that can be easily remedied.

Recommended Videos

Burnette breaks the files into two groups: one set of 37 files zipped up in a directory of materials to provide audio support for particular chipsets, and another set of seven files that are in the “unit test” portion of the source tree. While the unit tests are part of the Android source code, they aren’t actually compiled into the final Android product: they’re simply there to let developers and QA folks double-check the validity of software builds. The unit test files have been rebuilt using a decompiler from the versions originally offered by Sun and have apparently had an Apache software license incorrectly applied to them. As of earlier this month, Google had removed all the files from the Android source tree.

Oracle’s suit against Google rests on issues other than de-compiled unit tests and headers included in audio drivers; Mueller’s assertion was that elements of the public Android source code seemed to add even more fuel to Oracle’s assertions that Android infringed on their technology. Even assuming none of Mueller’s recent assertions bear out, the fact remains that Oracle is suing Google over Android, and—so far—Google hasn’t mounted much of a defense.

Topics

Google

Former Digital Trends Contributor

Geoff Duncan writes, programs, edits, plays music, and delights in making software misbehave. He's probably the only member…

Computing

We just got our first hint of the RTX 6090, but it’s not what you think

A hand grabbing MSI's RTX 4090 Suprim X.

As we're all counting down the days to a possible announcement of Nvidia's RTX 50-series, GPU brands are already looking ahead to what comes next. A new trademark filing with the Eurasian Economic Commission (EEC) reveals just how far ahead some manufacturers are thinking, because it mentions not just the Nvidia RTX 5090, but also an RTX 5090 Ti; there's even an RTX 6090 Ti. Still, it'll be a long while before we can count the RTX 60-series among the best graphics cards, so what is this all about?

The trademark registration filing, first spotted by harukaze5719 on X (formerly Twitter) and shared by VideoCardz, comes from a company called Sinotex International Industrial Ltd. This company is responsible for the GPU brand Ninja, which doesn't have much of a market presence in the U.S.

Computing

How the Blue Screen of Death became your PC’s grim reaper

The Blue Screen of Death seen on a laptop.

There's nothing more startling than your PC suddenly locking up and crashing to a Blue Screen of Death. Otherwise known as a Blue Screen, BSOD, or within the walls of Microsoft, a bug check screen, the Blue Screen of Death is as iconic as it is infamous. Blue Screen of Death is not a proper noun, but I'm going to treat it like one. It's what you were met with during crashes on Intel's 14th-gen CPUs, and it littered airport terminals during the recent CrowdStrike outage.

Everyone knows that a Blue Screen is bad news -- tack on "of Death" to that, and the point is only clearer. It's a sign that something catastrophic has happened, so much so that the operating system can't recover, and it needs to reboot your PC in order to save it. The Blue Screen of Death we know today, fit with its frowning emoticon, is a relatively new development in the history of Windows.

Computing

The performance downgrade made to the M4 Pro that no one is talking about

Someone using a MacBook Pro M4.

I've spent this whole week testing the new M4 chip, specifically the M4 Pro in both the Mac mini and 16-inch MacBook Pro. They are fantastic, impressive chips, but in my testing, I noticed something pretty surprising about the way they run that I haven't seen others talk much about. I'm talking about the pretty significant change Apple made in this generation to power modes.

First off, Apple has extended the different power modes to the "Pro" level chips for the first time, having kept it as an exclusive for Max in the past. The three power modes, found in System Settings, are the following: Low Power, Automatic, and High Power. The interesting thing, however, is that in my testing, the Low Power drops performance far more this time around.