News for hackers. Stuff that matters.
Re:The case against Kotlin by fulafel on Sunday July 30, 2017 @03:06AM (#14884797)
The semantics is the major pain point. It doesn't flag many errors. Python is a much easier language to dev/debug in because of this. Also, if you're going to transpile, why not transpile from a nicer language? ES6 is competing with ClojureScript/TypeScript/etc.
Re:The case against Kotlin by srean on Sunday July 30, 2017 @03:38AM (#14884894)
Is the 'transpile' nonsense a java script community thing ?
Re:The case against Kotlin by shakna on Sunday July 30, 2017 @12:00PM (#14886497)
Transcompile is very old term in computing, at least the 80s, specifically referring to compiling from one language, to another high level language.

CoffeeScript simply made the shortened term more popular, but the use of a more specific term is nothing to get irritated about.

Re:The case against Kotlin by fulafel on Monday July 31, 2017 @09:35AM (#14891777)
True, but transcompiling hasn't been a very commonly used term for that so it's not an obvious term to use. For example, the early C++ compiler that targeted C was not referred to as a transcompiler. Nor was the popular f2c fortran-to-c compiler.
Re:The case against Kotlin by fulafel on Sunday July 30, 2017 @03:48AM (#14884914)
Yes, I guess "compiler" confused too many developers who thought it implied native code.
Re:The case against Kotlin by abiox on Sunday July 30, 2017 @07:59PM (#14888584)
"transpiler" is a subset of "compiler".