Re: Dynamic Languages [was: Re: why Obj-C]
Re: Dynamic Languages [was: Re: why Obj-C]
- Subject: Re: Dynamic Languages [was: Re: why Obj-C]
- From: James Duncan Davidson <email@hidden>
- Date: Mon, 8 Apr 2002 16:37:11 -0700
On Monday, April 8, 2002, at 03:07 , John C. Randolph wrote:
Whatever form such a future language/developement environment takes, I
want it to blow away the compile-debug-edit cycle. (Joy's Active
Developer looks like a good start on this, BTW.) I want to keep my
source code in a fully relational database, where I can say "build the
app as it was last Wednesday", or "use the November 12 baseline, except
for these five classes I'm working on".
I used VisualAge enough to know that I didn't like this mode of
operation--at least as it's been implemented to date. CVS sucks, but it
handles the above needs to manage code at least somewhat well. Now, if
somebody makes a database managed system that still leaves me with files
in the filesystem and the ability to use other tools on the code besides
the IDE that is all knowing abot the database backend, then we might
have something.
I want *live* editing/patching of the code in a running instance of the
app, and I want to be able to trivially rollback changes made to the
code, or to any data the app was working on.
The was a Java VM that briefly existed that did this. You could change a
method implementation and the next thread to go through the method would
pick up the new one. Pretty impressive stuff. But it got lost somewhere
along the way. Probably since JITs/HotSpot have world views that the
code is static (for obvious performance reasons) -- and class loading
under Java was always "interesting".
duncan
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.