Also, OpenJDK is now 12 years old... It seems like forever, and it's kind of weird that events that old are still relevant to live legal disputes, but... I guess that's the speed of software vs. the speed of the U.S. legal system... ;)
149 karma · joined May 5, 2019
Also, OpenJDK is now 12 years old... It seems like forever, and it's kind of weird that events that old are still relevant to live legal disputes, but... I guess that's the speed of software vs. the speed of the U.S. legal system... ;)
Conversely, by Oracle's logic, any application that uses the Java API would be a derivative work (the method signatures are perfect copies), and thus the app would need to be either GPL itself or pay for a commercial license for Java. This, too, seems incompatible with existing practice (e.g., Apache's Java applications are licensed under its own open-source license which is more permissive and thus can't be a derivative work under the GPL.
What am I missing here?
There were also some upsides to the competition in terms of motivation and focus, though admittedly with extremely ambitious law students it was a little over the top for the first year. But based on my experience teaching undergraduates, the middle ~60-70% of the class would benefit from an environment with more immediate competitive pressure.
The downside is that there's definitely a learning curve and you get packages like this early in the process. The upside is that it's bringing a whole bunch of new people in who are willing (and increasingly more able over time as they learn) to help write new open-source software.
A much more accurate system, IMHO, would be to switch over to a ranking/percentile order within the school, and use standardized tests for rough cross-school comparisons. Sure, it's not perfect, but it seems better than what we have now.
Also, it provides a great argument for instructors when students inevitably come-a-grade-grubbing. "I can't bump your score, because that would inexorably bump DOWN someone else's score, and that wouldn't be fair to the other students."
Choosing how to respond to a query string is the very nature of what a search engine does. It's utterly impossible to have one without the other. The more charitable interpretation of your argument is that there should be more "neutrality" in the algorithm, but that's also difficult... Should they be neutral to whether or not people are trying to manipulate algorithms with dishonest SEO? Should they be neutral to what other users like? Neutral to who else links to the page? Who decides which neutrality prevails where they conflict? Who decides if a certain kind of neutrality is more important than user preferences or market demands?
This is a rabbit hole of mutually exclusive goals and inevitable trade-offs that requires complex judgment. Government regulation in this area would be extremely difficult and troublesome, not just for economic reasons but also for first amendment ones. Free market competition in this area is going to be limited due to economies of scale, so that isn't perfect either.
And if you think that imposing traditional publisher liability for search engines is likely to make search engines censor _less_, you might want to think a few steps further down the strategic consequences.