Well no, not really. I mean, yes, I guess it technically did. Then it got decimated again. And then it got decimated 12 more times.
Well no, not really. I mean, yes, I guess it technically did. Then it got decimated again. And then it got decimated 12 more times.
http://en.wikipedia.org/wiki/Decimation_(Roman_army)#Current...
You're wrong. And you're the worst kind of wrong: pedantically wrong. Please stop.
There are other, better, words available that can take its place.
Because, I mean, if you're going to be That Guy etc. etc., being right is close to the only thing you've got left.
Now, don’t get me wrong, the etymology of words is intensely interesting. It always makes me happy to learn how words were originally used and how that meaning changed – but all that doesn’t help you decide what a word actually means right now.
Argue against using the word. Don’t dare argue that it has a different meaning than it actually has.
Also, I think I will increase my use of decimate. If it pisses off those annoying pedants (who are perfectly aware of what is being communicated and won’t be the slightest bit confused) I will be happy. I successfully communicated and pissed off people I don’t like. Yay!
But I like you...
You'll make a lot of friends with that attitude.
1. Kill, destroy, or remove a large percentage of. 2. Drastically reduce the strength or effectiveness of (something): "plant viruses that can decimate yields".
Lots of words change meanings, and hundreds of years is usually enough time for a new meaning to become totally unobjectionable. But I think the main issue here is that the word so clearly derives from the Latin for "ten" that it just sticks out like a sore thumb.
The Spanish word diezmar, shockingly enough, also means to destroy (or cut by a tenth), even though it looks like it's got a ten in there, too.
Diesmo, on the other hand is quite common and I guess you can say that diesmar is the act of giving the tenth of your profits to the church. Still, diezmar is a dead word.
Instead we use decimo for tenth and decimar for destroy.
Type either "blob" or "binary lob." PLEASE!
Most (traditional) relational database servers do not support arbitrary sized (often >255 bytes) fields in a single row. The solution was to have a separate Large OBject heap, and store references to those LOBs in the actual rows.
Starkey claims that he invented the term, and that the acronym is actually a backronym. I've heard conflicting stories on that score.
But I'm kinda curious what you thought it stood for?
In the context of 'binary blob' I think it would be clear it just means an amorphous mass of bits and not some Jargon File definition (which in turn is clearly a play on the regular word in itself).
I expected most people here to know this. I've been proven wrong.
I understand better the origin of the confusion, though.
I am! I didn't even know blob was meant to be an acronym (or, in fact, anything other than what the word "blob" suggests) before this discussion, so, to me, binary blob always meant binary lump of goo-like stuff.
He's just talking about of how are blobs in drivers evil for BSD, taking advantage of the evil amoeba concept.
[I agree, the word binary is redundant (nobody complains about source blobs), but not because it's an acronym. The phrase "unfree blob" would also be redundant, since blobs are unfree by definition.]
Anyway, BSD's usage is not actually the general use of the word, as you can see in the link I've posted somewhere else in this nitpicking thread, people usually mean a bunch of bytes, without connotation.
There is one correct use, and three other uses talking about "binary blobs" without a negative connotation.
My opinion is that the layman term got mixed up with the database term and thus we got this mess (should I say blob?)
Language is constantly evolving, especially as it pertains to words taken from other languages.