comment on

Thanks for your comprehensive response!

BTW there is a new Yún which just came out. I think this will wind up being the best approach to IoT stuff. In other words the two-tiered approach with a WiFi chip running OWRT and an AVR running the actual control with a bridge between them just like the Yun has.

I guess what I would love to see stripped down, lightweight Perl at the OpenWRT level for HTML-based UI development and MQTT and stuff like that. Some simple, fast, lightweight Perl combo that has some Web-UI development stuff and MTTQ stack too, plus some common crypto stuff.

Also your approach using rbpi and an avr via serial is great too. But I think that the two tiered approach using owrt and the avr on the same board is awesome.

In reply to Re^2: What do we have to do to resuscitate micro Perl? I want Circuit Perl NOW! by ait
in thread What do we have to do to resuscitate micro Perl? I want Circuit Perl NOW! by ait

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks