News for hackers. Stuff that matters.
Re:The case against Kotlin by sidlls on Saturday July 29, 2017 @07:05PM (#14883435)
I primarily use Python, C++ and Rust these days and I would certainly moan about having to pick up JavaScript.
Re:The case against Kotlin by celim307 on Saturday July 29, 2017 @07:54PM (#14883611)
When have you used it last? The ecosystem around it sucks but the language itself is not too bad, es6 has made the syntax pretty bearable
Re:The case against Kotlin by harrygeez on Sunday July 30, 2017 @12:44AM (#14884472)
I just started using it recently and while writing in Babel/ES6 is nice, figuring out which framework or libraries to use (React vs Web Components and React vs Vue vs Polymer vs Angular vs...), sass or less, to redux or not, setting up webpack is definitely not an enjoyable experience. The beauty of many other languages is it doesn't usually involve so many decisions. There's usually an undisputed better library, a recommended setup, but js ecosystem now has so many options that it only leads to decision fatigue.
Re:The case against Kotlin by bsder on Saturday July 29, 2017 @10:31PM (#14884091)
> The ecosystem around it sucks but the language itself is not too bad

The problem is that the ecosystem is what matters nowadays. A language can suck donkey balls and win as long as it has a robust ecosystem (see: VB6, PHP, etc.)

Python and Rust have phenomenal ecosystems. I have no clue about the C++ ecosystem nowadays.

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".
Re:The case against Kotlin by abiox on Saturday July 29, 2017 @08:37PM (#14883779)
undefined is not a function!
Re:The case against Kotlin by jackmott on Saturday July 29, 2017 @08:16PM (#14883700)
ugh
Re:The case against Kotlin by sitkack on Saturday July 29, 2017 @07:19PM (#14883493)
Funnily enough, the list of complaints was almost a perfect mirror of C++ dev complaining about Rust.
Re:The case against Kotlin by sidlls on Saturday July 29, 2017 @08:22PM (#14883732)
That doesn't even make sense. There is absolutely no parallel in going from Java to JavaScript with going from C++ to Rust.