From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Richard Elberger" To: <9fans@cse.psu.edu> Subject: RE: [9fans] source code as data not text Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <20010618184843.68F9819A00@mail.cse.psu.edu> Date: Tue, 19 Jun 2001 19:36:41 +1200 Topicbox-Message-UUID: bd12700c-eac9-11e9-9e20-41e7f4b1d025 Yes, I think my wording was too general. Yes, too many shells like sh and ksh, but I wasn't thinking a cmd line shell -- just would like to see a standard wrapper for the handling of code, how it maps to business (or other) process -- like if a "feature module" will be plugged in or not to the build, and how that is managed/operated, knowing where the code was coming from, what environment it was written in, what scenarios/environment it was unit tested in, etc ... a lot of things to track and imo it is all important (though varying in degrees of importance). Kind of like an app, but it is basically a software team's creative bucket -- a system that is self-enclosed and shares namespaces (be it source, devices, or workspaces). So much stuff and syntax checking is just part of an app that is part of what should be a consistent system to minimize risk. I already thought of styx, and how it would be excellent to leverage this for a full-on collaborative development environment. It would be a huge undertaking to create something like this, and it would be very exciting. -- rich >-----Original Message----- >From: 9fans-admin@cse.psu.edu [mailto:9fans-admin@cse.psu.edu]On Behalf >Of David Gordon Hogan >Sent: Tuesday, 19 June 2001 6:49 a.m. >To: 9fans@cse.psu.edu >Subject: RE: [9fans] source code as data not text > > >> I would rather have code stored in a >> clustered rdbms that is accessed through its own shell [that is >> cross-platform like limbo] > >The last thing we need is another shell. > >What if the code were accessed through a file system interface >which is cross-platform? > >