I thoroughly enjoyed this, though the author did present as fact, many of today's tenuous theories (e.g. animatter, microscopic black hole!). http://qntm.org/destroy
...And I hope that someday That you, you people will all have the chance To read The Helping Friendly Book And experience the wisdom Of the great, the great and knowledgeable Man who wrote The Helping Friendly Book Because he is, the great and knowledgeable He is the one, the only author of The Helping Friendly Book He is the man The great man The only, the special His name is The author of The Helping Friendly Book He is the great The knowledgeable, the one and the only The great, the knowledgeable Person who wrote The Helping Friendly Book His name could only be The one, the only, the only, the special The author of The Helping Friendly Book... -Excerpt from Icculus by Phish There are few mantras that are as universally agreed upon by Software Engineers as Don't Repeat Yourself or DRY. It rings deeply and globally true that any form of code duplication is at best a compromise, at worst, an abominable trap. Writing and maintaining...
What I wish to address is this: "With the rise of virtualization, applications will transform into virtual appliances. Virtual appliances simplify application deployment by delivering the complete software stack—from OS to the application—as a single, integrated unit." -SDTimes Web Seminar Abstract Lest I be seen using VMs and am accused of being hypocritical: Virtualization is great for configuration testing. There is no better way to test against Oracle or Windows 98 without having to install such icky things than a VM. "Virtual Appliances", however, are a different story. Though they may “seem” exciting, and may be a practical solution given today’s technology and today’s problems, I find the trend disturbing. Why? ...Because a) the entire approach is grossly inefficient; and b) this is just another chapter in the long history of industry repetition. Setting aside the inefficiency aspect for a moment, isn’t this form of “run anywhere” virtualization exactly...
I continue to ponder how to merge the Relational Model (RM) and Object Oriented (OO) worlds in order produce a best-of language. The task is a challenge due to the deep and fundamental differences between OO and the RM. One approach I am exploring is to utilize the notion of multiple logical representations to allow both to co-exist without compromise. Doing this, though, means pinning down canonical isomorphisms between the two models. One important concept from the OO world is polymorphism. In OO land, we identify a useful abstract concept like "Contact" and build a class around it. We then build classes for more specific types of contacts such as Organization and Person. A challenge for me has been to identify a clearly obvious equivalent to this design in relation land. This has proven quite elusive because there are several relational designs that seem to qualify. The design that seems most commonly used involves a "type" table of some sort followed by tables c...
Comments