On Fri, May 15, 2009 at 2:41 PM, Carol Farlow Lerche <c...@msbit.com> wrote: > Since you grant my premise, the corollary is that it wouldn't hurt to have > mono installed. See here about the mono footprint on disk and in memory.
That's so simplified that is stupid. Let's avoid such simplifications here. I'll introduce a new major runtime if there is a major "killer app" it brings. I am trying to add high-value functionality while _removing_ memory footprint so XS-on-XO is viable. So 2 examples to compare: - The mono code we're looking at would replace 40 lines of PHP, and add the burden on me of maintaining a bit of the XS in yet another language and toolkit. - ejabberd has been an incredible timesink, every time we want to do something with it, it takes a very long time because few people know erlang, and while I've learned a lot about it, I'm slow with it. But it's worth it: no other jabber server is as efficient (memory/cpu) as ejabberd. Overall, I am painfully working to reduce the mem footprint so that XS-on-XO is viable. Similar efforts are needed on the Sugar side to keep it viable on low-power platforms. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel