Slashdot Mirror
Judge In Oracle-Google Case Given Crash Course in Java
itwbennett writes "Lawyers for Oracle and Google gave Judge William Alsup of the U.S. District Court in San Francisco an overview of Java and why it was invented, and an explanation of terms such as bytecode, compiler, class library and machine-readable code. The tutorial was to prepare him for a claim construction conference in two weeks, where he'll have to sort out disputes between the two sides about how language in Oracle's Java patents should be interpreted. At one point an attorney for Google, Scott Weingaertner, described how a typical computer is made up of applications, an OS and the hardware underneath. 'I understand that much,' Alsup said, asking him to move on. But he had to ask several questions to grasp some aspects of Java, including the concept of Java class libraries. 'Coming into today's hearing, I couldn't understand what was meant by a class,' he admitted."
You would need to be some sort of mechanical or engineering background information, however, to determine if party B's mechanical system is different enough from party A's mechanical system to rule on some sort of patent issue between the 2 parties. To one person, an engine is an engine. They don't care if it's petrol, diesel or rocket fuel. It's the loud bit that makes vehicles move.
Someone determining whether or not the latest engine by VW (for example) is too similar to an engine previously made by Alfa Romeo is going to need to know more than "an engine is the loud bit that makes vehicles move" - somebody is going to have to explain the details behind the mechanics. Based on this information, they might decide that the engine as a whole isn't a rip-off, but maybe the odd way the valves are set up is suspiciously similar. It would be unfair to make a judgement without the extra technical knowledge.
...he doesn't pretend to be a developer.
Awesome Judge!
I am very small, utmostly microscopic.
How is the judge going to learn enough about Java, in a way that is unbiased by the lawyers for each side, in a few weeks, to make a sensible decision? Doesn't he need to know a fair bit about how Java code is used, who uses it, what for, etc?
He needs to understand the concepts of Java, not all the implementation details and not how to code/debug/code/scream/debug/sigh/debug/relief java. And he doesn't need to be able to read Java or its syntax.
A quick overview of Java features that are not unique to Java will also help eliminate a lot of the clutter. He needs to understand using or extending classes (ie, the Java class libraries) but not have to worry about all the possibilities of public/private properties & methods, inheritance, polymorphism or other common OOP mechanisms.