<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 27, 2016 at 1:45 PM, Felipe Magno de Almeida <span dir="ltr"><<a href="mailto:felipe.m.almeida@gmail.com" target="_blank">felipe.m.almeida@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Sep 27, 2016 at 2:26 PM, Vladimir Prus <<a href="mailto:vladimir.prus@gmail.com">vladimir.prus@gmail.com</a>> wrote:<br> ><br> > Hi Rene,<br> <br> [snip]<br> <span class=""><br> >> And the really hard question.. What of the current b2 implementation,<br> >> design, ecosystem, is getting in the way of reaching the above wishes?<br> >> And if you dare.. What should we change to move forward?<br> ><br> > I am obviously biased; but I think the Jam language is holding us back.<br> > Absolutely nobody know it, and anything not natively supported by the<br> > language requires code in C, with awkward bridging.<br> <br> </span>The move away from Jam would be, IMO, the single most important<br> thing we can do to make b2 more widespread. Writing extensions<br> are a fact of life, and doing them in jam is just really, really, really<br> painful.<br></blockquote><div><br></div><div>Check.</div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">-- Rene Rivera<br>-- Grafik - Don't Assume Anything<br>-- Robot Dreams - <a href="http://robot-dreams.net/" target="_blank">http://robot-dreams.net</a><br>-- rrivera/<a href="http://acm.org/" target="_blank">acm.org</a> (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail</div></div> </div></div>