3 ms·
> I think there's value in explaining what a blob is: without any context, it's not a meaningful term. The problem with the backronym for this is that it's pla
by tialaramex 4y ago
> I think there's value in explaining what a blob is: without any context, it's not a meaningful term.
The problem with the backronym for this is that it's plainly wrong. Which didn't matter in the context in which it was created, it reminds me of the R.V.Jones story about why H2S (a second world war radar system) was called that, you mustn't say it's because the big boss said "It stinks", and that reminded the chemists on the team of H2S, the formula for rotten egg smell -- that would make the boss look bad - so you pretend it stands for "Home Sweet Home" even though that makes no sense because it is for identifying bombing targets.
The blobs Debian cares about aren't necessarily "Binary", it's just as much a problem if we're obliged to send 4MB of inexplicable ARM assembler text to a remote device, or if the firmware is base 64 encoded (and thus ASCII text) for some daft reason. If Binary just means "Of course they are because it's a computer" see Object.
The blobs Debian cares about aren't necessarily "Large" either, what would constitute "large"? If I've got 64 bytes of firmware that are fed to an 8501 controller that's probably its entire program, but it's way smaller than this paragraph of text. Does large just mean "Non-zero size" ?
So that leaves us with "Object", which I mean, I guess? It's as vague a word as blob was.