<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Stéphane.<div><br></div><div>I enjoyed reading your thoughts in this matter. ^__^ Let's see how we can provide and maintain those layers and switches. Maybe they don't have to be "rather wide" at all.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 30.05.2020 10:30:16 schrieb Stéphane Rollandin <lecteur@zogotounga.net>:</p><div style="font-family:Arial,Helvetica,sans-serif">> I still prefer having an opened platform to being lock in own autistic <br>> world, but sometimes i wonder until which limit it is really worth...<br><br>This remark has a wide and deep reach and applies pretty much to any <br>life situation, individual or collective. In short, where is the limit <br>between 'self' and 'the rest of the world'?<br><br>Since there is no definite answer to this question then maybe, following <br>the traditional Smalltalk way, should we reify it and construct the <br>proper objects and protocols able to deal with its different specific <br>aspects- have classes reflecting the 'external world' so to say.<br><br>In other words, the implementation details of the external systems do <br>not have to enter the image, but there could be a (rather wide) layer of <br>abstraction within the image that tells the rest of the system what is <br>outside and how we are interfaced to it, with switches to allow, for a <br>given situation, either to retract in our autistic world (where backward <br>compatibility and resilience are ensured) or open up to a specific API, <br>(where the risk of obsolescence and deprecation exist, but are then made <br>explicit and dealable with).<br><br>Just hand-waving here...<br><br>Stef<br><br></div></blockquote>
</div></body>