Language Selection

English French German Italian Portuguese Spanish

OpenSolaris axed!

Filed under
OS




OpenSolaris

And MySQL will be next.

oh yeah

but anyone not living in fantasy land had to see it coming. That's why folks have been working out fork plans ahead of time.

no big surprise here.

Big Bear

Oracle v. Google

Back in my server admin days, I tried both MySQL and PostgreSQL. Both were great, but I preferred PostgreSQL and ended up using it. In short, we don't need no stinkin' MySql, Java, Oracle, or Microsoft .NET, or even Openoffice.org. Let this be a lesson to those lovers of Mono.

For those wanting to keep up with Oracle v. Google, Groklaw intends to maintain meticulous coverage.

re: PostgreSQL

Remains to be seen if most of the popular app's (i.e. blog's, cms's, wiki's, forum's, etc) will be coded to support Postgresql.

Until that happens, I doubt that many non-enterprise users will jump ship from the Mysql boat.

Oracle v Google: Why?

redmonk.com/sogrady: When Android debuted in 2007, I couldn’t figure out how Google had managed to apply an Apache license to the project. Java, like Linux, was governed by the GPL and thus incompatible with the more permissive license Android was sporting.

Stefano Mazzocchi subsequently answered the Java related questions: Google wasn’t using Sun’s VM, they’d built their own. As had Danger before, from whence many of the Android team arrived. Called Dalvik, Google’s cleanroom reimplementation was, if not “Sun’s worst nightmare” as Mazzocchi put, a clear fork-in-the-eye to the Java license holders. However brave a face they put on it at the time.

Whether Google decided to reimplement the JVM for financial reasons, technical reasons, or both, is unclear. Whatever the motivation, Dalvik allowed Google to bypass Sun en route to market. What Dalvik never did – never could have done – was protect Google from patent litigation.

In estimating the risks of such action, Google could have reasonably assumed that the probability of Sun suing them was near zero.

rest here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Rust 1.9

  • Announcing Rust 1.9
    The Rust team is happy to announce the latest version of Rust, 1.9. Rust is a systems programming language focused on safety, speed, and concurrency.
  • Rust 1.9 Released
    Rust 1.9 brings controlled unwinding support, support for deprecation warnings, new targets (MIPS Linux Musl C library and i586 Windows MSVC), compile-time improvements, more library stabilization work, and new Cargo features.

Announcing the Open Source License API

Over the last 19 years, the Open Source Initiative (OSI) has been the steward of the Open Source Definition (or OSD), establishing a common language when discussing what it means to be an Open Source license, and a list of licenses which are known to be compatible with the OSD. This is taken to its logic next step this year, with the OSI providing a machine readable publication of OSI approved licenses at api.opensource.org. This will allow third parties to become license-aware, and give organizations the ability to clearly determine if a license is, in fact, an Open Source license, from the authoritative source regarding Open Source licenses, the OSI. Read more

Leftovers: Gaming

Win for APIs and FOSS (Android Case)

  • Google beats Oracle at trial: Jury finds Android is “fair use”
    Following a two-week trial, a federal jury concluded Thursday that Google's Android operating system does not infringe Oracle-owned copyrights because its re-implementation of 37 Java APIs is protected by "fair use." The verdict was reached after three days of deliberations. "Ladies and gentlemen of the jury, listen to your verdict as it will stand recorded," said the court clerk, before polling each of the ten men and women on the jury. There was only one question on the special verdict form, asking if Google's use of the Java APIs was a "fair use" under copyright law. The jury unanimously answered "yes," in Google's favor. The verdict ends the trial, which began earlier this month. If Oracle had won, the same jury would have gone into a "damages phase" to determine how much Google should pay. Because Google won, the trial is over. "I salute you for your extreme hard work in this case," said US District Judge William Alsup, who has overseen the litigation since 2010. "With the thanks of your United States District Court, you are now discharged. I would like to come in the jury room and shake each of your hands individually." Four of the ten jurors declined to comment to reporters gathered in the hallway. The other six went out through a back exit. "We're grateful for the jury's verdict," said Google lead lawyer Robert Van Nest before getting into the elevator with Google's in-house lawyers. "That's it." Oracle attorneys had no comment.
  • Google wins Oracle copyright fight over Android code
    Today, a jury in California's Northern District federal court declared that Google's use of copyright-protected code in Android was fair use, freeing it of any liability. Oracle, which controls the copyright on the code, had been seeking $9 billion for the use of the code. The case centers around an API developed by Java and owned by Oracle, which allows outside programs to easily interact with Java programs. Android uses the same API, and in 2014 a federal appeals court ruled that Oracle has a valid copyright claim on the API code, potentially putting Google on the hook for billions of dollars in damages. (The Supreme Court declined to hear the appeal.) In the latest round, Google argued that Android's reimplementation of the API constituted fair use, which would allow use of the code without invalidating Oracle's copyright. Ultimately, the jury found that case convincing.