On Thursday, March 3, 2022 at 11:42:10 AM UTC-6 [Offray] wrote:

> I like the definition of architecture as the stuff that is difficult to 
> change
>
... 

> [1] "Good Enough" Architecture: https://youtu.be/PzEox3szeRc
> [2] Architecture: The Stuff That's Hard to Change 
> https://youtu.be/3LtQWxhqjqI
>
> These videos discuss organizational-level issues. I have no experience at 
this level, and you shouldn't take anything I say to apply to this level. 
When I talk about architecture I am speaking of Leo's architecture at the 
module and class level.
 

> the distinctive factor would be the kind of understanding and 
> conversations that a live coding environment is enabling between the 
> user/dev and the artifact itself and how this have consequences in the 
> creations/tasks at hand
>
... 

> [3] https://vimeo.com/38272912
>
This video, Inventing on principle, is indeed intriguing. The underlying 
language isn't smalltalk, so the same ideas could, I suppose, be used in 
python. Afaik, the source code isn't available. I assume, as a kind of 
reverse engineering, that Victor has enhanced the drawing and "physics" 
portions of the game app. It's a cool demo.

>
> [4] https://www.youtube.com/watch?v=Pot9GnHFOVU
>
> The moldable development environment shows what is possible when 
fundamental objects can be augmented. It's an interesting idea.

*Summary*

Thanks for these links. The first two deal with system design issues that 
do not relate directly to programming languages. The second two links 
relate to issues closer to my world.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/e29aac4f-23e0-4ea9-b7bd-5080e1bb1bdfn%40googlegroups.com.

Reply via email to