Google wins crucial API ruling, Oracle's case decimated
arstechnica.com
arstechnica.com
On the other hand, when defining language itself, all I can really come up with is "a generally agreed-upon form of communication." If enough people agree that "decimated" means "destroyed" (as I thought it did), then doesn't that in itself morph the language?
Then there's the big-picture view: the language is going to morph by general consensus whether or not I agree with it.
If you really like the original meaning, then you should increase its usage in as originally meant so that there's a reason for dictionaries to place the original definition next to the ones that other people actually use in real life.
All those in favor of me increasing its usage, please form a line.
http://instruct.westvalley.edu/lafave/DFW_present_tense.html
I won’t go past your first sentence because I already sound like an ass. But you see what I mean: language changes over time. Meanings are lost or transformed or extended by analogy and, though it may pain us, “incorrect” uses abound and eventually become the norm. You don’t have to like it or agree with it, but it does happen, and prescriptivism gets you nowhere in discussions of language.
As I wrote in another reply, I think I just really like the original meaning of decimated and I feel it's a shame to lose that due to popular [mis]use, even if that's just how language works.
[Edited to remove logical argument and replace it with sentimental one.]
Googling “define:decimate” gave me:
1. Kill, destroy, or remove a large percentage of
2. Drastically reduce the strength or effectiveness of
Which is in line with most people’s understanding of the term, and makes no mention of the original meaning.
The problem with prescriptivism is that the rabbit-hole goes back to the very beginning of language itself. You could start saying an ekename (from eek meaning other) instead of a nickname, or a napron instead of an apron because these words arose from misdivision. You could revert to pronouncing fir, fur, and verse with different vowels. You could bring back the eo diphthong and say seolfor for silver and geolu for yellow.
But you wouldn’t, because that’s absurd, and I contend that dragging our heels against any language change is equally absurd.
> I contend that dragging our heels against any language change
> is equally absurd.
If by "any" you mean "all", then I agree. With "decimated", the meaning "one-tenth" is still an accepted current definition rather than an anachronism. So I choose to selectively drag my heels and cherry-pick definitions when it comes to words I enjoy.So Oracle's argument is now (or has been) 'it's copyright infrignment if you copy part of it, but not if you copy all of it!'
Good luck with that.
>Some speculated an Oracle win could have scared programmers away from Java, but that kind of ruminating is a moot point now.
I'm not so sure they had to win to make that happen. Bringing this case forward in the first place was a great step in destroying the Java platform. And it wasn't even their first step, though it's gotten more attention than anything else so far.
Oracle is killing Java. The metaphor of the goose that lays golden eggs is terribly apt, here.