<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 17/06/2020 à 12:44, Douglas Brebner
via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:e4ad954a-394d-d010-8fe9-606e6e640cc1@gmail.com">
<div class="moz-cite-prefix">On 17/06/2020 11:17, Hilaire
Fernandes via Cuis-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8556e64a-3c53-7ad6-8660-0f342d99c9cc@drgeo.eu">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
- <b>namespace</b> for safe installation of
applications/bundles,
<p>- <b>sandbox environment</b> for safe execution of
applications/bundles,</p>
</blockquote>
<p>I've recently been thinking of some kind of Actors in the form
on sub-images or mini images ran in parallel that may be a way
to handle those cleanly.</p>
<p>Inspired somewhat by Alan Kays comment about how the computer
should be split into smaller computers. Objects don't quite have
the properties to be that (due to Process) but the Image *does*.</p>
</blockquote>
<p>Oh yes this is wise. Even stronger, we do not have the choice
given the single thread nature of the VM, it will be a waste of
resources to not have several image running in parallel. I vaguely
know that there are inter process protocol for communication
between process (IPC). Should it be fast enough for communication
between applications deployed in different images?<br>
</p>
<p>Likely a Dynabook will be based on ARM architecture. The A64 SoC
shipped with Pine64[1] comes with 6 cores! Using only one will be
a waste of resources.<br>
</p>
<p>Hilaire<br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://www.pine64.org/">https://www.pine64.org/</a><br>
</p>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a>
<a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre>
</body>
</html>