<story><title>Quark – A software sketchbook for your projects</title><url>https://medium.com/hackernoon/announcing-quark-a-software-sketchbook-for-your-projects-2f53553415b</url></story><parent_chain></parent_chain><comment><author>masukomi</author><text>&amp;gt; ...felt a need for a software tool that would help me do things like — plot charts, app prototyping, create dashboards&amp;#x2F;GUI’s for my personal projects etc. I just needed “some place” to write my code, build small projects or test new ideas. To much of my own surprise, I could not find an easy way to do so.&lt;p&gt;to the author: Congrats on building and delivering on what&amp;#x27;s a pretty significant undertaking.&lt;p&gt;That being said, Smalltalk has had the capabilities you were looking for, for ages, and the tools are incredibly polished because they&amp;#x27;ve been around for so long. On a related note Glamorous Toolkit &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gtoolkit.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gtoolkit.com&amp;#x2F;&lt;/a&gt; takes those capabilities and points them at development itself allowing you to use them to help figure out what your code and data are &amp;#x2F; are doing.&lt;p&gt;This is an interesting project, but it&amp;#x27;s just the beginning of recreating what already exists in Pharo smalltalk. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;pharo.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;pharo.org&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Quark – A software sketchbook for your projects</title><url>https://medium.com/hackernoon/announcing-quark-a-software-sketchbook-for-your-projects-2f53553415b</url></story><parent_chain></parent_chain><comment><author>writepub</author><text>- sketches will have a dependency on the electron version used by Quark&lt;p&gt;- sketches are effectively extensions installed over quark, much like VS-Code extensions. They come with the same advantages, and drawbacks of being tied down to what the &amp;quot;platform&amp;quot; offers, the platform being Quark. If quark makes opinionated decisions on architecture, you&amp;#x27;re limited by it&lt;p&gt;- uncompressing to an in memory file system and using that as the app binary unnecessarily increases RAM&amp;#x2F;CPU footprint&lt;p&gt;- each &amp;quot;sketch&amp;quot; is likely to spawn it&amp;#x27;s own JavaScript node context, at the very least. Maybe even it&amp;#x27;s own chrome content context, for isolation and security purposes. How exactly does this take the same resource as a single electron app? The likely increase is comparable to [New Chrome Tab + Node context]. It&amp;#x27;s lower than a whole new electron app, but probably averages 60MB-ish in RAM, and the overhead of 2-3 new precesses</text></comment>