Skip to content
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.

why JS? #3

Open
earlence opened this issue Apr 8, 2016 · 2 comments
Open

why JS? #3

earlence opened this issue Apr 8, 2016 · 2 comments

Comments

@earlence
Copy link

earlence commented Apr 8, 2016

Doesn't running JS require too many resources (jscript interpreter, thread support etc). Shouldn't the translators be lightweight, without bringing in all the baggage that JS brings?

@matheusmonte
Copy link

I think choice JS is because have a lot of people who develop on JS. But I know that is heavier than another languages like c++. Is most popular than C++ and mote acessible

@jeanpa
Copy link

jeanpa commented Apr 11, 2016

earlence and matheusmonte - your are both correct: We started with JS because JS is known by many people and we hope many people write translators to their favorite things. We also hope to work with the cross-platform JS community to continue building robust cross-platform libraries for the different protocol buses used to communicate with “Things”. That said, in scenarios where JS requires too many resources, I hope the community will analyze those scenarios and the community could decide later to build support for other languages.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants