3 ms·

Disclaimer: the below text is just my opinion meant to answer the Parent's questions about my preferences. Please do not take it to be an attempt at starting a

Disclaimer: the below text is just my opinion meant to answer the Parent's questions about my preferences. Please do not take it to be an attempt at starting a flamewar (or, for that matter, an invitation to do so). I have never enjoyed dynamic typing; it has always seemed like TheWrongSolution™ to me. And Haskell really drives that home for me (i.e., it is possible to have a static type system with all the benefits that gives you without any of the headaches). Additionally, I really dislike the trend of JS moving out of the web browser; it is incredibly easy to write impenetrable JS (particularly with the compile-to-js languages) which makes it much harder for me to understand what is running on my system, how to contribute to it and how to debug it. Furthermore, JS is fast in comparison to other interpreted dynamic languages, but is quite slow compared to most native code (like the kind you would get with Haskell). I am not trying to be one of the JS naysayers that gets into religious wars, but I will say that I am generally not a fan of the language, and the possibility of removing it from my life does seem like a net-positive. But again, my intention is not to start a flamewar, simply answer your questions about my preferences.

vmorgulis 11y ago
I understand your point of view. I see asm.js and wasm as an evolution path. The same idea as JVM bytecode but twenty year after. It can provide the cross-platform and ubiquity advantages to most of existing projects and languages.
deleted 11y ago
[deleted]
woah 11y ago
Your choices are totally sensible. What I meant was the idea that everyone is just waiting for JS to go away seems like you're extrapolating your preferences onto other people.
- halosghost 11y ago
  Well, while I would like to see many of the cool JS projects out there written in a language I am more amenable to (and thus, would like to see an end to JS), I recognize that not everyone agrees. So, in the meantime, I have the unfortunate stance of not using many of those projects that I would otherwise be interested in. Though, if a significant number of people feel similarly to me (that there are better options than JS and that wasm could catalyze the move towards those better options), then I do not really see a problem with JS going away. Perhaps that is just me. Again, I did not write this post with any intention of flaming or insulting those who like JS.
- saosebastiao 11y ago
  He extrapolated to me quite well. The existence of hundreds of languages that compile to javascript is pretty good proof that there are tons of people that are waiting for JS to go away.
  - halosghost 11y ago
    Or, at the very least, that there are many people that feel unsatisfied with JS in its current form.
- rpcope1 11y ago
  I think there are is a sizable contingent of those of us, who do not like Javascript (or the often impending callback hell that comes with a language not initially designed with concurrency in mind); the HN echo chamber may lead you to believe otherwise, but I personally will be very happy when I can skip the Javascript altogether, and pick a language I find more amenable when I get goaded into doing front-end development.

vmorgulis 11y ago

I understand your point of view. I see asm.js and wasm as an evolution path. The same idea as JVM bytecode but twenty year after. It can provide the cross-platform and ubiquity advantages to most of existing projects and languages.

deleted 11y ago

[deleted]

woah 11y ago

Your choices are totally sensible. What I meant was the idea that everyone is just waiting for JS to go away seems like you're extrapolating your preferences onto other people.

halosghost 11y ago
Well, while I would like to see many of the cool JS projects out there written in a language I am more amenable to (and thus, would like to see an end to JS), I recognize that not everyone agrees. So, in the meantime, I have the unfortunate stance of not using many of those projects that I would otherwise be interested in. Though, if a significant number of people feel similarly to me (that there are better options than JS and that wasm could catalyze the move towards those better options), then I do not really see a problem with JS going away. Perhaps that is just me. Again, I did not write this post with any intention of flaming or insulting those who like JS.
saosebastiao 11y ago
He extrapolated to me quite well. The existence of hundreds of languages that compile to javascript is pretty good proof that there are tons of people that are waiting for JS to go away.
- halosghost 11y ago
  Or, at the very least, that there are many people that feel unsatisfied with JS in its current form.
rpcope1 11y ago
I think there are is a sizable contingent of those of us, who do not like Javascript (or the often impending callback hell that comes with a language not initially designed with concurrency in mind); the HN echo chamber may lead you to believe otherwise, but I personally will be very happy when I can skip the Javascript altogether, and pick a language I find more amenable when I get goaded into doing front-end development.