decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
And lose Java? It's about a big cat and a very small bag. Or big cow, small barn? | 234 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
And lose Java? To move all JAVA houses to something else, would take 5-10 years at least.
Authored by: Anonymous on Thursday, April 19 2012 @ 07:54 AM EDT
When you have mountains of code already out there being used by
real users. To move and THEN MIGRATE all that to something else.
Would take a really long time before it could be done.

Then, folks would also look at the cost of it, LABOR would be
really expensive to even think about writing all the code new
again. So, their bean counters would then look at the license
cost vs writing everything from scratch, and guess what would be
cheaper. So, they would most likely stay with, and gladly pay
for the cheaper license vs the huge cost and TIME it would take
before they could even start to test their new "other language"
code against their existing JAVA based install.

[ Reply to This | Parent | # ]

And lose Java? It's about a big cat and a very small bag. Or big cow, small barn?
Authored by: Anonymous on Thursday, April 19 2012 @ 08:04 AM EDT
Remember the whole list of "licensees" mentioned in this case
almost from the start, where it seems that Google is the only one
that elected not to license (their cat that fully left the bag)?

IBM and others (a long list) HAVE a license (maybe from early on,
before JAVA was licensed under the free license), I don't know
how long. But, they are seen by Oracle, those other licensees,
and their customers, as cows that Oracle wants to milk again in
the future.

This Google direction, if others follow it, well...
that is the cat that they want put back in the bag.

Big cat, small bag.

Or, rather in the view of Oracle, a very big cow that they seem
to want to get back in their very small barn.


[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )