3 ms·
Any time you use anything non-native, you add layers of indirection and potentially lots of impedance mismatch between languages/runtimes. For instance, I know
by RussianCow 7y ago
Any time you use anything non-native, you add layers of indirection and potentially lots of impedance mismatch between languages/runtimes. For instance, I know all of the ones you mentioned would be non-starters at my current job because it means we would have to wrap all of our JS libraries/APIs in the language of choice, which is a non-trivial amount of work. Plus, debugging becomes more challenging as you're basically having to do it at two levels simultaneously.
Even with all of JavaScript's deficiencies, it's still far easier to just deal with them than to switch languages entirely.
- lagg 7y agoI too remember the time when we didn't assume there'd be a Makefile-ish system that has to bundle everything, compile the sass, pull bootstrap, etc. Then there's the map files for debugging that will generate cleanly every now and then. I've adapted but these strange abstraction languages are still where I'm drawing the line. At a certain point it's like, are you choosing the language for the project or is it the other way around. Hah, I just remembered Vala. Edit: Also this thread and the internet in general make me feel bad for liking javascript. It has issues with the global namespace being all wrecked when used for DOM, but the language in and of itself I just find cool for the same reason I find JSON and the way lisp treats objects/data/code cool. So many playa hataz :(