<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></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 21.09.2017, at 12:23, Jesper Louis Andersen <<a href="mailto:jesper.louis.andersen@gmail.com" class="">jesper.louis.andersen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Wed, Sep 20, 2017 at 12:50 AM Richard A. O'Keefe <<a href="mailto:ok@cs.otago.ac.nz" class="">ok@cs.otago.ac.nz</a>> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One question. I can get a<br class="">
"Raspberry Pi 3 Model B with 1.2GHz 64-bit Quad Core and 1GB Ram"<br class="">
for NZD 69 including tax and run Erlang on it.<br class="">
(Hmm. Next time I have some spare cash I must get one...)<br class="">
<br class="">
Why would I pay NZD300 for a 300MHz board with 64MB of memory?<br class="">
<br class=""></blockquote></div><div class="gmail_quote"><br class=""></div><div class="gmail_quote">My prediction is that eventually we'll see the "small embedded" market squeezed down by rather cheap powerful devices such as the rPI. My argument for this prediction hinges on power becoming free in the future (due to the current massive advances in solar and wind energy on top of better batteries).</div></div></div></blockquote><div><br class=""></div>Small embedded being current rPI *sized* CPUs for some definition of small will be happening. Except rPI is not usable in production for several reasons (supply, quality, hardware changing beyond your control). </div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote">Currently, the power draw of the stronger chips is too high and production at scale means that shaving off a few cents here and there is worth it.</div></div></div></blockquote><div><br class=""></div>Exactly. We have a few industrial applications where we would love to get a larger CPU but we can’t because of price and power (meaning in this case thermal energy output).</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote">But it looks like the price tag of a 1.2 GHZ 64 bit chip is only going one way, and this makes the added development effort of targeting a smaller chip more expensive. In turn, you need an even bigger scale of production. And so on.</div></div></div></blockquote><div><br class=""></div>Except that with a 300MHz Cortex M7 size CPU you can do lots of interesting applications just in Erlang already and save the costs. </div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote">GRiSP is interesting because it can offer you a far faster time to market and lower development effort at the same or better robustness/resilience. You can thus get the lower production costs while amortizing development effort better. It is a good bet until the niche squeeze I predict above happens.<br class=""></div></div></div></blockquote><div><br class=""></div><div>Thanks :-) </div><div><br class=""></div><div>Also we plan not to be squeezed but adapt. One size which is just getting viable with Erlang are the automotive controllers with flash and ram on the CPU only (for the automotive industry any external memory is too unreliable and a problem for EMC). Thats one direction what I want to target with the GRiSP software stack. </div><div><br class=""></div><div>We could have easily also targeted a 24 core communication controller with 16 times Gbit I/O which is a tempting target also and noone would complain about the compute power there ;-)</div><div><br class=""></div><div>For the GRiSP-base we just tried to pick the right sized board for today. Others might follow…</div><div><br class=""></div><div>Best,</div><div>-- Peer </div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class="">
_______________________________________________<br class="">erlang-questions mailing list<br class=""><a href="mailto:erlang-questions@erlang.org" class="">erlang-questions@erlang.org</a><br class="">http://erlang.org/mailman/listinfo/erlang-questions<br class=""></div></blockquote></div><br class=""></body></html>