News for hackers. Stuff that matters.
Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by reikonomusha on Thursday December 24, 2015 @01:06PM (#10789022)
While as you point out there's not necessarily an academic difference, the notion that your target language will itself require a compiler and/or runtime is useful to know up front. Transpilers also usually attempt close to 1-to-1 translation. Functions become functions, constants become constants, etc.

As someone who has written many compilers before, I'd almost feel it would be a slight disservice to call a transpiler a compiler, mostly because their architecture and goals are often different.

Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by hellofunk on Thursday December 24, 2015 @01:18PM (#10789065)
I think the distinction is useful too, as it gives you a better idea of where a language actually sits in a development workflow.
Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by progman on Thursday December 24, 2015 @04:51PM (#10789688)
Then why not just use the term "translator"?
Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by reikonomusha on Thursday December 24, 2015 @11:59PM (#10790470)
Translate usually means something bijective.
Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by meric on Thursday December 24, 2015 @06:20PM (#10789899)
I think it's fine to call it a compiler if it compiles a language to another of a lower level of abstraction, which may be true with compiling lisp to javascript, depending on if macros and read macros were implemented. There's just no way a programmer can manipulate the reader in javascript.
Re:Making a Mini-Lisp: Introduction to Transpilers in JavaSc... by 0_00_0 on Thursday December 24, 2015 @07:24PM (#10789997)
Eval? Code as as string, parse, analyze, etc. Then code gen the JS you need into a string. Eval the string.