Daniel Shahaf wrote on Mon, 17 Jan 2022 10:24 +00:00: > Sam Ruby wrote on Sun, 16 Jan 2022 21:26 +00:00: >> On Sun, Jan 16, 2022 at 1:49 PM Dominik Psenner <[email protected]> wrote: >>> Could a comparison with a house be of help? A house is something specially >>> made according to the specifications of the owner and adapted according to >>> meet its requirements and fulfill needs. A house can be built of bricks, >>> stone, wood, .. and there are various things that nees to be assembled by >>> experts of their own right. Maybe there is a good analogy to find what >>> logging means for a house. It could be a printer that protocols to paper >>> what the house is doing, a door gets opened and closed, water that is >>> running and stops to do so, an oven thats baking,... >>> >>> If one gets to understand what log4j is in this house, it is surely easier >>> to explain java, jndi and ldap with analogies as well? >>> >> >> I actually don't think we go there. Essentially there is a recall on a >> thingamabob. Most people don't know how cars work either, but when they >> get a recall, they take it in to get fixed. What's different here is that >> it is not just one model or even make of a car that is getting recalled, >> but rather a large number of different manufacturers that are affected. >> And they are wondering why this is, and want to make sure that it doesn't >> happen again. >> > > It's simply a cache invalidation problem. It has nothing to do with > open source (either the class of licenses or the software development > paradigm).
And to answer why it affects so much stuff: because it's basically the equivalent of a recall of copper wire, fingerprint marks on surfaces, or the letter "e". It's all over the place and people don't keep track of everywhere it is at. (And the copies don't "phone home" to check for updates, neither to the software's developers nor to whoever installed it.) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
