The only way it could be worse would be if they ruled that what Google did isn't fair use as a matter of law. If you read the decision, they almost did that, but didn't. I hope this is reheard en-banc or the Supreme Court takes the case. This is a nightmare.
I have very little respect for the Federal Circuit. They seem to cause many more problems than they solve. And, here, they took Ninth Circuit precedent and twisted it to say the opposite of what it meant. The Ninth Circuit gives interoperability concerns serious consideration; this decision gives them much less consideration than they deserve.
For Google's particular case, there looks to me to be an easy way out. All Google has to do is distribute its work under the GPL, since Java, including the APIs in question, is under the GPL anyway. The "Classpath exception" was Sun's explicit consent to use the APIs in Java without needing the work to be GPL as well. So, as long as Google distributes its work as a "modified version of OpenJDK", they should be good. I'm not sure why they haven't done this already, or didn't do it to begin with, actually. Perhaps I'm missing something, but I can't see what.
But this goes way beyond Android and Java. This ruling, if it's not overturned, could chill software development, promote extreme forms of vendor lock-in, and otherwise cause mayhem and misery.
What is the best way to construct a compelling story for upper management so they'll appreciate the hard work that an IT department does? They don't seem particularly impressed with functioning systems, because they expect functioning systems. The extensive effort to design and implement reliable systems has also made IT boring and dull. What types of summaries can you provide upper management to help them appreciate IT infrastructure and the money they spend on the services it provides?"
The aerial images from the drones were able to create broad maps of the area that were detailed enough to show damage. The team took drone maps of the various villages and got them physically printed, as many of the communities aren’t online.
Here's the final ruling.
The proposal, expected to be outlined on Friday before the Common Council's Public Transportation Review Board, not only lifts the cap on taxicab vehicle permits but accommodates new smartphone app services such as Uber and Lyft. Both Uber and Lyft are already in the marketplace.
It's not surprising, then, that in every city in AT&T's 22-state footprint where Google is considering deploying fiber, AT&T also plans to bring GigaPower. That's a total of 14 markets, including Austin, the Triangle region of North Carolina, and Atlanta, home to AT&T's mobility division. While AT&T refuses to acknowledge that its gigabit fiber plans are answering the competitive challenge posed by Google Fiber, others say that Kansas City may have been a wake-up call. 'I think all the providers have learned some valuable lessons from Google's Kansas City deployment,' says Julie Huls, president and CEO of the Austin Technology Council. 'What Google did instead was say, "We're going to build you a Lamborghini, but price it at the same price as a Camry,"' says Blair Levin. 'And that's what's so disruptive about it.'"
They have now introduced the 'Commerce Expansion Adjustment' whereby some sales are made through methods such as carrier billing and the developer will only get 56.1%.
There is no option for developers to opt out of this type of sale; Microsoft suggests that 'You may want to consider if the Commerce Expansion Adjustment applies in a country/region where your app is available and factor that into your market pricing strategy'
As a veteran of the store pricing wars on Palm OS, I have seen how this plays out. Stores competed to sell through new partners, and offered increasingly large shares of revenue to those partners. Inevitably, that came out of the developer share.
I would be very happy for Microsoft to offer me an option to make additional sales at a lower revenue share — but I'm not happy at being forced to suck it up.