News for hackers. Stuff that matters.
Re:Electron considered harmful by marcosdumay on Thursday November 24, 2016 @02:16PM (#13032185)
First, X-only programmers are obviously wrong, whatever is the value of X.

That said, yes, somebody ought to love JS in a not blind way. Big numbers work that way. If that's you, I don't think those comments are for you. All languages have different flaws, every flaw relevance varies by context, and contexts are incredibly subjective. Yet, some contexts are much more common than others, and many people preach in support languages that are harming them because they don't know any better.

Re:Electron considered harmful by k__ on Thursday November 24, 2016 @03:06PM (#13032451)
I did C, C++, Java, PHP, VBA and JS and can't tell why so many people have constant beef with JS. I mean especially after all major platforms have adopted ES2015.
Re:Electron considered harmful by marcosdumay on Friday November 25, 2016 @05:24AM (#13035657)
For me, IO in JS is still kind of a hack. It still imposes an structure on my code that is different from the one I want.
Re:Electron considered harmful by pluma on Friday November 25, 2016 @09:23AM (#13036881)
IO in what? The browser? Node? If you mean node, what IO specifically? `http.createServer`? `fs.readFileSync`? `fs.createReadStream`? `fs.open`? `fs.readFile` with node callbacks? Promises? Streams? Observables?

Without context it sounds like you saw a bunch of nested callbacks in a Node.js example and judge the entire language based on that.

Re:Electron considered harmful by pluma on Friday November 25, 2016 @09:29AM (#13036919)
You'd be surprised how many people I've met that enjoy JavaScript. Nearly everyone I've met that hates JavaScript either didn't bother to learn it ("It's just a scripting language") or is just upset that they can't use their favourite programming language all the time (this is how we ended up with CoffeeScript, Sass and Haml and why everything in the Java world is eventually wrapped in XML).

I've seen enough different use cases and teams and programming languages to understand there's no point in being arrogant about language choice: if a team already knows a given language, it is most likely the right tool for the task, unless the benefits of replacing it are worth the overhead of properly switching to and gaining competence in another language.