I've already blogged about the security problems caused by CDO and worse still, how CDO brought the world to its collective financial knees, but apparently the problems with modeling aren't isolated to that trouble making CDO component. Not at all! The problem seems to be a general Eclipse Modeling Framework shortcoming. It must be a fact because I just read about Microsoft's March Security Bulletin where the article makes it clear that "The problem stems from the way that the operating system parses and displays Windows Metafile- and Eclipse Modeling Framework-formatted image files." If that doesn't make your icicles shiver, nothing will!
Every community needs a scapegoat, so I say we pick on EMF. After all, if you have a really bad design, you can always blame EMF for generating it that way. Not only that, if you have really bad algorithms that perform poorly, you can always blame EMF for being bloated and slow. I've even heard that EMF isn't thread safe! Nothing distracts better than a scapegoat and EMF is really the ultimate scapegoat. If I'm reelected to the Eclipse board---you only have until Friday to vote for me---I promise to get to the bottom of this type of problem and root out the causes whomever they may be. No one will be safe from my careful scrutiny. We will reinstate public flogging to maintain order and discipline. Clearly I'm the no-nonsense candidate of choice.
Metrology in mining and metallurgy
4 years ago