<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 30, 2017, at 3:26 PM, Shannon Spires <<a href="mailto:svs@bearlanding.com" class="">svs@bearlanding.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I'm much more in Matt's camp on this issue than the CLIM camp.</span></div></blockquote></div><br class=""><div class="">One of the things that I liked about MCL (and HyperCard, and SK8), is that they all facilitated a style of UI programming in which you could instantiate some widgets and plug them together and inspect them and adjust them and reprogram them interactively until they were just right. That style made it fast and easy to plug together a working UI by experimentation. I very much like that style of working.</div><div class=""><br class=""></div><div class="">I haven't used CLIM very much, but my impression is that it's not so much like that. Is that a wrong impression?</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>