I do not see why live coding programming languages could not manage their source code in versioning control system. To me, people opposing live coding and released/versioned software are just **PLAIN** idiots. Period. You can have a live reflective system and still want to have a fully reproducible built system. This is what we do with Pharo. We manage everything with a version control system and still Pharo is fully dynamic. And No not everybody can commit and change Pharo. About large and complex systems, I heard that an insurance company has 30 Millions lines Smalltalk application. and this system is live and also versioned! Hopefully. So do not lose your energy with idiots. Stef On Wed, Jul 19, 2017 at 8:18 PM, jWarrior <dmacq@erols.com> wrote:
Well .....
I worked on JWARS for 13 years until the Navy killed it at the end of 2010, and I have never heard of Miles Fidelman. JWARS was run almost exclusively in SCIFs (secure facilities), and most of the users did not have access to the source code. So I do not know where Miles gets his information.
JWARS had extensive version control. All new versions of the main config maps were tagged with extensive information about what was included.
I agree with what Richard says below, "I suspect Miles doesn't really understand what a âlive coding environmentâ really means.", although I would phrase it less gently.
-- View this message in context: http://forum.world.st/Can-anyone-answer-this-tp4955861p4955916.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.