<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Sketching in Hardware 2013: Physical Computing with JavaScript</title><link>/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/sketching-in-hardware-2013-physical-computing-with-javascript</link><description>I have attached slides from Jason Kridner&amp;#39;s Physical Computing with JavaScript presentation at Sketching in Hardware 2013 ( http://sketching-in-hardware.com/ ).
Attachments: community.element14.com/.../Jason-Kridner-_2D00_-Physical-Computing-with-JavaSc</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Sketching in Hardware 2013: Physical Computing with JavaScript</title><link>https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/sketching-in-hardware-2013-physical-computing-with-javascript</link><pubDate>Wed, 31 Jul 2013 17:57:05 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f1685422-3ff6-481a-83e4-85237d02f99e</guid><dc:creator>shabaz</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;Great slides! &lt;/p&gt;&lt;p&gt;Initially in the past I had been confused, because since Javascript runs on the browser, (and I hadn&amp;#39;t heard of Node.js) I was a little confused and had thought that I&amp;#39;d need a browser opened on the BBB to make use of bonescript, so I&amp;#39;d ignored it all.&lt;/p&gt;&lt;p&gt;Now it&amp;#39;s much clearer that this is the Javascript engine, but doesn&amp;#39;t need a browser to run in. It&amp;#39;s very cool, since Javascript is a fairly friendly language (in the past, for what little I&amp;#39;ve done, I&amp;#39;ve relied on javascript libraries heavily to make sure that it works consistently across browsers, but I&amp;#39;m sure that has changed now - or at least is a non-issue in this case, since there is only one Node.js engine).&lt;/p&gt;&lt;p&gt;It&amp;#39;s also extremely powerful&amp;nbsp; that you can use other existing js libraries! That sounds pretty amazing. I can&amp;#39;t wait to try that out. And create http based UIs without needing Apache and PHP.&lt;/p&gt;&lt;p&gt;Possibly this can all be done with Python too (I don&amp;#39;t know) but I&amp;#39;m convinced js+bonescript is worth paying a lot of attention to, to rapidly develop applications - and in a language that is literally designed for the web, so lots of knowledge reuse for those who will one day want to create web apps.&lt;/p&gt;&lt;p&gt;The ideal scenario for some apps could be PRU&amp;lt;-&amp;gt;C/C++ and then IPC with Node.js javascript (and bonescript for any direct hw control) for the http based UI.&lt;/p&gt;&lt;p&gt;Also, I wonder how performance compares with a typical desktop browser running JS.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=15834&amp;AppID=80&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>