News for hackers. Stuff that matters.
Re:Colony, an experimental JavaScript-to-Lua compiler by fab13n on Wednesday October 26, 2011 @05:19PM (#3160475)
In which cases would anyone need:

- to write code in JS rather than in Lua;

- and run the result on a platform which supports Lua but not JS?

Except in a Dilbert-like situation, where a clueless middle manager decides that using a dirty hack is safer than letting JS programmers take the 2 days it would take them to become very proficient in Lua, I can't think of one.

Re:Colony, an experimental JavaScript-to-Lua compiler by zhemao on Wednesday October 26, 2011 @05:33PM (#3160533)
Many C applications use Lua as an embedded scripting language. This program would be very useful if the developers of the application wanted to extend scripting support to Javascript (and compile-to-JS languages) without having to modify their C code.
Re:Colony, an experimental JavaScript-to-Lua compiler by fab13n on Thursday October 27, 2011 @04:27PM (#3165358)
But a transcompiler will always be a kludge, at least when the target language hasn't been designed as a bytecode.

Most importantly, I'd bet that the intersection of developers who:

(1) can write good software; and

(2) Can write decent JS code, but can't become proficient in Lua within a couple of days;

is mostly empty.

Re:Colony, an experimental JavaScript-to-Lua compiler by finnw on Wednesday October 26, 2011 @05:47PM (#3160585)
But if they are developers why would they not want to modify their own C code (to add an embeddable JS interpreter?)
Re:Colony, an experimental JavaScript-to-Lua compiler by aaronblohowiak on Wednesday October 26, 2011 @08:46PM (#3161123)
js interpreters are not as friendly as lua for embedding.
Re:Colony, an experimental JavaScript-to-Lua compiler by zhemao on Wednesday October 26, 2011 @10:40PM (#3161394)
Exactly, I've worked with the Lua C API before, it was fairly easy to use. I've looked at the V8 API before. Compared to Lua, it is far more complicated.