XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
=?utf-8?B?UmU6IFt4bWwtZGV2XSBXaGF0IGlzIHRoZSDigJxzdGFuZGFyZCBm?==?utf-8?B?b3Jt4oCdIG9mIGRhdGE/?=

> 
> I respectfully disagree. From the reading that I have done on the early days of UNIX, some very smart people developed some really good coding principles. From my perspective, those principles are timeless. For instance, does anyone disagree with this principle that they developed 50+ years ago: "A program should be viewed as just a stage in a larger process. Stages should be simple and easy to connect." 
> 
> In my opinion, an idea should be based on its merit, not its age.
> 

Database technology, centred on the capabilities of large direct-access disks, emerged at about the same time as UNIX, and the initial design of UNIX failed to take account of it (the filestore permissions model, for example, is totally unsuited to database-centric applications). The UNIX concept of pipelines is a great way of organising batch jobs, but it really doesn't fit into the world of database-driven transaction processing, which is a completely different, and equally valid, paradigm.

Michael Kay
Saxonica 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS