News for hackers. Stuff that matters.
Re:Tessel, a NodeJS-based microcontroller by waterlion on Thursday September 05, 2013 @08:26AM (#6333659)
I don't understand this craze to use JS everywhere. It's not the best language for every job. The main argument seems to be 'if you know JS you can use it in product X'. If you're not competent enough to learn another language then are you competent to write good enough JS?
Re:Tessel, a NodeJS-based microcontroller by joeblau on Thursday September 05, 2013 @10:06AM (#6334239)
The community is one of the best development communities out there. Node + NPM have created an ecosystem with lots of contemporary tools that fall in line very well with the UNIX Philosophy. The few people that I've shown Node to have been surprised about how easy it is to use NPM and tackle dependency management.

> If you're not competent enough to learn another language then are you competent to write good enough JS?

I used to say that about Java Developers that didn't know C/C++. As I've grown, the thing I've realized is that the end user/customer/client doesn't care what you write your application in (Unless you're on a Government contract). They care if it works.

Re:Tessel, a NodeJS-based microcontroller by egeozcan on Thursday September 05, 2013 @08:34AM (#6333705)
I think in this case there are a few reasons:

1) Node.js has a huge ecosystem and it's easy to use

2) JavaScript is known by many

3) JavaScript may not even come close to being a proper language for hardware programming but it is good enough for these kind of devices

Re:Tessel, a NodeJS-based microcontroller by drdaeman on Thursday September 05, 2013 @11:43AM (#6334836)
> Node.js has a huge ecosystem

So do many other platforms.

> JavaScript is known by many

So are many other languages.

> JavaScript [...] is good enough for these kind of devices

So are many other languages.

The question, as I got it, was "why JavaScript is chosen among many possibly alternatives?". Your comment does not answer it, I believe.

Re:Tessel, a NodeJS-based microcontroller by egeozcan on Thursday September 05, 2013 @08:52PM (#6338117)
Even if you used the same argument for all my points, the intersection of the result sets seems to be empty.

To be more clear, AFAIK, no other platform accomplishes those three goals as good as JavaScript. Maybe Python? GitHub language stats used to say otherwise (until they removed them). I also have the impression that as far as dynamically typed languages go, JavaScript is one of the most optimized ones. Well, Lua and some others beat it on speed but they are not as popular and/or provide what node.js provides.

Re:Tessel, a NodeJS-based microcontroller by reustle on Thursday September 05, 2013 @09:45AM (#6334118)
Also, the event loop seems work well with these fun hardware projects
Re:Tessel, a NodeJS-based microcontroller by drdaeman on Thursday September 05, 2013 @11:48AM (#6334871)
You can have event loop in any language that has enough access to underlying OS facilities (select/poll/epoll/kqueue) out there. Can't name a non-esoteric language where you can't off the top of my head.
Re:Tessel, a NodeJS-based microcontroller by cliffbean on Thursday September 05, 2013 @12:23PM (#6335062)
It's not just a theoretical question about whether a particular language is capable of supporting an efficient event loop. It's also a significantly practical question about whether there are a large number of libraries and community experience built up around programs organized this way.

This is also one of the big reasons why the people who wrote node.js picked JavaScript in the first place [0].

[0] http://s3.amazonaws.com/four.livejournal/20091117/jsconf.pdf

Re:Tessel, a NodeJS-based microcontroller by drdaeman on Thursday September 05, 2013 @01:12PM (#6335393)
Any reason large number of libraries should even know about they're using evented/async IO? I believe most of them consist of purely sequential actions (say, "connect then send then receive then process then return") and gain no benefit from non-blocking (function-wise, not program-wise) IO. If the core is smart enough to run them as coroutines (for example see Python's gevent.monkey) that yield back to event loop on waiting for IO, they'll automagically do the right thing without being infested with CPS callback ladder hell.
Re:Tessel, a NodeJS-based microcontroller by thedufer on Thursday September 05, 2013 @11:53AM (#6334898)
JavaScript is built around events and the event loop in a way that few languages are, which makes it well-suited to a hardware environment like this.
Re:Tessel, a NodeJS-based microcontroller by cliffbean on Thursday September 05, 2013 @12:12PM (#6335000)
Also, this is not just a property of the language itself, it's a property of the ecosystem built around the language.
Re:Tessel, a NodeJS-based microcontroller by vertex-four on Thursday September 05, 2013 @12:08PM (#6334982)
Not really? Javascript interpreters, and the DOM tend to be (and Javascript interpreters only are because they're geared towards being embedded in browsers, primarily). The language isn't any better for it than any other language that supports closures, though.
Re:Tessel, a NodeJS-based microcontroller by thedufer on Thursday September 05, 2013 @02:11PM (#6335796)
> The language isn't any better for it than any other language that supports closures

Which puts it pretty high up to begin with. Factor in the number of libraries that assume an event loop (all of them that care either way) and that are asynchronous by default because of this (most of them) and it becomes pretty hard to beat.

Re:Tessel, a NodeJS-based microcontroller by bryanlarsen on Thursday September 05, 2013 @09:44AM (#6334110)
Many embedded projects these days do command and control via a small web server. So you've likely got a fair amount of JavaScript in your project anyways. The rest is often written in a combination of c and Lua. Lua might be a better language than JavaScript in isolation, but it might be better to avoid the cost of context switching your brain several times a day.
Re:Tessel, a NodeJS-based microcontroller by jffry on Thursday September 05, 2013 @10:11AM (#6334273)
Tessel actually transpiles JavaScript into Lua, which is what is actually running on the device.
Re:Tessel, a NodeJS-based microcontroller by gruseom on Thursday September 05, 2013 @01:16PM (#6335418)
In that case they've buried the lede, as this is arguably more noteworthy than the microcontroller. Has anyone done a production-worthy JS-to-Lua compiler before? The idea has come up many times because the two languages are so similar. But I've not seen anything as complete as what they must have if they're running Node. (What about the non-JS parts of Node? Can those just be handled with a standard compiler?)

JS-to-Lua might not be well-suited to this sort of platform, since it is so easy to just write Lua instead. But it would be useful if you want to get existing JS code running on new hardware, or if you want your program to be able to run in a web browser as well.

Re:Tessel, a NodeJS-based microcontroller by legutierr on Thursday September 05, 2013 @11:21AM (#6334704)
That's cool. Do you know what library they use to do the translation?
Re:Tessel, a NodeJS-based microcontroller by jffry on Thursday September 05, 2013 @12:50PM (#6335232)
I don't, but their FAQ says that they will be open-sourcing their code and hardware.
Re:Tessel, a NodeJS-based microcontroller by jnbiche on Thursday September 05, 2013 @11:30AM (#6334753)
Oh, way cool. Did you build the transpiler in-house?
Re:Tessel, a NodeJS-based microcontroller by jffry on Thursday September 05, 2013 @12:49PM (#6335226)
I don't work for them, I just read the FAQ at the bottom of TFA:

  | What's running JavaScript under the hood?
  | We're currently running a custom-built, real time operating
  | system on top of a Lua Runtime. Your JavaScript is compiled
  | to Lua bytecode when you push your code, and that bytecode
  | is run on the runtime. It's this runtime that allows us to
  | have such low memory overhead. We may switch over to an
  | implementation of Libuv or a microLinux flavor in the future,
  | but that shouldn't change anything about the user experience
  | with Tessel (except it will be faster!)
Re:Tessel, a NodeJS-based microcontroller by jffry on Thursday September 05, 2013 @08:33AM (#6333693)
I think it's fine for rapid prototyping. It has WiFi and is positioned for internet-connected stuff. There are lots of people who use node.js and packages from npm to interface with internet services, so this gives them an easy way into working with an embedded device without a large learning curve.
Re:Tessel, a NodeJS-based microcontroller by waterlion on Thursday September 05, 2013 @08:39AM (#6333733)
There are lots of Python libraries too, and PIP. This wasn't necessarily a dig at just this platform but the general principle of re-inventing multiple wheels, except this time with JS.
Re:Tessel, a NodeJS-based microcontroller by MatthewPhillips on Thursday September 05, 2013 @09:50AM (#6334141)
Python can run on a microcontroller too[1], do you think that's a bad as well? I can't figure out what your criticism is: that they choose not-C or that they specifically choose JavaScript?

[1]https://wiki.python.org/moin/PyMite