3 ms·
The same thing happened to VisualWorks Smalltalk years ago. We reimplemented the "change log" to use XML, so we'd be buzzword compliant. Functionality gain: n
by stcredzero 17y ago
The same thing happened to VisualWorks Smalltalk years ago. We reimplemented the "change log" to use XML, so we'd be buzzword compliant. Functionality gain: none. Result: embarrassing bugs in Smalltalk training class when I was demoing how you don't lose code even if your image crashes.
(We broke a very cool feature that had been working for decades, which is core to developers, just to be buzzword compliant!)
- eugenejen 17y agoSo did the new feature break the object reflection inside smalltalk image? I like to hear more details about this.
- stcredzero 17y agoNope. There was just a bug that broke the re-reading of the change log. It was fixed pretty quickly. But not before I had a chance to show a bunch of Smalltalk students VisualWorks flailing.
- petercooper 17y agoNow the title of Robert Martin's talk: "What Killed Smalltalk Could Kill Ruby Too" makes sense.. http://railsconf.blip.tv/file/2089545/ http://railsconf.blip.tv/file/2089545/
- stcredzero 17y agoYes, and it pains me to see you guys making the same mistakes. (Though, you have done some things really right!)