That's realtime coding, then. Which ultimately includes anything with a repl.
We already have a constraint there (time). I think that time-in-front-of-an-audience is a more accurate one.
On 27 December 2015 22:16:37 GMT-08:00, David Barbour <dmbarbour_at_gmail.com> wrote:
>On Sun, Dec 27, 2015, 6:01 PM Rob Myers <rob_at_robmyers.org> wrote:
>
>>
>> > Live coding is using a powerful languages as an HCI.
>>
>> ...as a (public) performance.
>>
>
>I reject performance or exposing code as a requirement.
>
>Live coding could just as easily be used to buy and sell stocks, to
>control
>a robot for explosive ordinance disposal, to control a squadron of
>killer
>robots in war, to manage lights in a smart home, to create music, to
>dungeon master a tabletop RPG (managing mobs and world creation), etc..
>
>As an HCI, the language be an automated interface to **something** in
>near
>real time. I disagree with any constraints on the something.
>
>--
>
>Read the whole topic here: livecode:
>http://lurk.org/r/topic/7Be9PKbHVemNWI48kcgyn0
>
>To leave livecode, email livecode_at_group.lurk.org with the following
>email subject: unsubscribe
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Read the whole topic here: livecode:
http://lurk.org/r/topic/6wuDnQ36v6ZOy8s7PHmQq6
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Mon Dec 28 2015 - 07:35:57 GMT