71–80 of 105 posts
Earlier quoted context omitted.
I think you overestimate Node's popularity, compared to other languages on the server side.
How would you measure such a thing? NPM has more modules than any other language package manager, isn't that evidence that Node is at least somewhat popular?
Earlier quoted context omitted.
How would you measure such a thing? NPM has more modules than any other language package manager, isn't that evidence that Node is at least somewhat popular?
I didn't say it's not popular. I'm just saying Node's popularity is not even near to Java or PHP. But I agree that Node's/io.js hype is much louder nowadays :)
I find this topic to be intellectually insulting. You know that JavaScript has its (tens of thousands of) fans. Why tell yourself otherwise? Is your hatred of it so overwhelming that you're not even ready to admit to yourself that others disagree with you?
When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.
But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.
Earlier quoted context omitted.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
By that reasoning PHP must be amazing
Earlier quoted context omitted.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
> Node's popularity is a pretty dramatic counterexample to that assertion. Popularity has nothing to do with quality. Node is popular because so many people knew JavaScript anyway. JavaScript is popular because it was the only widely-supported programming language for the browser (other than ActionScript, which is itself an ECMAScript flavor).
And that has nothing to do with the discussion at hand.
The statement "Most of us use it because we have to" is pretty clearly refuted by the fact that no one had to use JS on the server-side, yet plenty still pick Node over other alternatives (even ones they know well).
If only there was some way to pull out a hunk of code so that it could be reused. Hm. Somebody should invent that.
For me QML/C++ (or other C++ UIs) and Xamarin make much more sense for native mobile coders. - Better native integration - Integration with the SDK tooling - Support of all three major mobile platforms - Performance As soon as I saw what React Native offers, it was meh for me.
API-wise, MoSync really stands out. Unfortunately, it is dead now. Same goes for Adobe Flex/AIR.
Is there an FRP library in iOS? The author states that React "feels superior" than FRP, so I'm curious what the comparison was.
ReactiveCocoa is a fairly mature FRP library from GitHub. It strikes me as a funny comparison. I agree that the react approach can feel like a better fit than FRP at the view layer, but it's not like there aren't positive reasons to use FRP/signal-based programming in your model layer or when wiring up your models to React views.
Earlier quoted context omitted.
Completely agreed. After reading that I was immediate put off about the rest of the article.
Why? Javascript is not without its thorns and glitches. What makes it perfect for this use, in your opinion? Is it just the general "I don't like something you like" reaction - in which case, what is it that he's wrong about here?
So using a project and disagreeing with it's entire purpose for existing is silly without further explanation of why javascript is bad for this type of thing.
In his argument he says they should be using Objective-C over Swift, which is just wrong. Apple says to use Swift, it's faster and easier to use.
Beyond not liking javascript as a language it's super fast and easy to learn why not make it so more people can start developing apps using that language. It will create better apps that phonegap apps.
Earlier quoted context omitted.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
> Node's popularity is a pretty dramatic counterexample to that assertion. Popularity has nothing to do with quality. Node is popular because so many people knew JavaScript anyway. JavaScript is popular because it was the only widely-supported programming language for the browser (other than ActionScript, which is itself an ECMAScript flavor).