Updated Discussion on Dynabook (markdown)

Discussion-on-Dynabook.md

@@ -179,11 +179,11 @@ Technically all these views are Morph instances representing the underneath mode
 
 **---JR**: We are speaking of free resources, so we have their source and the rights to use and modify them. Doesn't the answer to your question depend of the familiarity of the user with the programming language or scripts, or on the existence of high level tools to create and modify the simulations? If we took this statistic point of view, would the fact that more teachers use python or javascript than smalltalk prove anything? And as a second point, do we really expect the teachers to create the resources? Isn't it enough to reuse, mix, adapt,assess... free available educational resources? Are the ones available so bad, so unsufficient? And the educational institutions and volunteers have been creating resources for more than twenty years? Are they useless and have always been so?
 
-**---HF**: 
+**---HF**: So we will not know if PhET instances are models or just user applications... In dynamic knowledge model, the meaning of model must be understood clearly. A Model is an object or group of objects created and manipulated through a set of programming instructions, in a live interactive programming environment, this programming instruction are edited step by step. I don't understand your questions regarding free resources, your tone seems to indicate I discard them. Not at all, I see no reason they can't be used in the context of the Dynabook. I am describing what is a dynamic knowledge model and I choose to implement the Dynabook App in Smalltalk and not js+css+html because the later is terrible to manage complexity, although it benefits of the awesome job done by corporate like Google on the JavaScript VM regarding efficiency in execution (https://v8.dev).
 
-**---JR**: Then an easy question for you to answer: why the **Cuis environment**? I know you fell in love with SmallTalk many years ago, but explain why not you as a developer but the end user should prefer the developers use Cuis over javascript plus html5 plus css.
+**---JR**: Then an easy question for you to answer: why the **Cuis environment**? I know you fell in love with Smalltalk many years ago, but explain why not you as a developer but the end user should prefer the developers use Cuis over javascript plus html5 plus css.
 
-**---HF**: 
+**---HF**: First, I don't fall in love with programming language, I use the right tool to achieve what I want to do. Smalltalk let me handle the complexity far more easier that C++, the previous language DrGeo was code with. You can search the literature why. The user has no preference regarding the developer environment as long as he does not need to operate directly on the engine, in the contrary Smalltalk is more developer friendly.
 
 **---JR**: Is your project multiplatform? Does in run on Windows, Linux, Android, containers, usb drive...?