3 ms·

Not according to the millions of people who use and like JavaScript.

by Touche 10y ago

rubber_duck 10y ago
The quality of JS ecosystem speaks for itself.
- untog 10y ago
  The breadth of the JS ecosystem speaks for itself, too.
  - rubber_duck 10y ago
    Absolutely - multiple halfassed re-implementations of the same thing found in most languages std lib is a huge reason why the language is bad (remember the left pad fiasco ?), but the semantics of the language make it fundamentally flawed without breaking backcompat. JS ecosystem is actually quite bad when it comes to functionality - but they do have 10 versions of same thing for stuff they do have and each of those works only in specific scenario it was written in but nobody bothers to extend it and writes their own instead when they need to solve something similar because reading other's people JS is a nightmare. If anything the kind of breadth JS ecosystem has shows just how hard to maintain other people code is.
    - rpedela 10y ago
      What a gross over-generalization. Yes there are crap libraries just like any popular language. There are also great libraries just like any popular language. If there are multiple for the same purpose, it is usually obvious which is the best one. Since you brought up the left pad thing, yes there is a small minority within the JS community that takes the Unix philosophy of "only do one thing and do it well" to an absolute extreme. But that isn't indicative of the JS ecosystem as a whole.
      - rubber_duck 10y ago
        >There are also great libraries just like any popular language. Mind naming some ? I work on Angular 2, React and TS front end in my day job - those libraries are a joke compared to similar libraries in other languages. For example Angular 2 Dart is a huge productivity improvement - having done a prototype with ng2 Dart and implemented a full app in TS having a language with sane semantics, actual standard library and a build system built by someone who knows what they are trying to do vs someone who hacked something themselves and everyone kept piling on. React compared to something like Clojure + Reagent is a similar comparison although CLJS tooling is much less mature than Dart - just dealing with immutability in JS/TS is so tedious and full of boilerplate. Just recently I had to find a library that will let me pattern match URLs and extract parameters (eg. 'foo/:a/:b(?foo=:c&bar=:d)' => {'a':..., 'b':..., 'c':..., 'd':...}) - and every option out there failed to work with anything beyond basics and the implementations were horrible - and this is JS core competency.
        rpedela 10y ago
        You are claiming that JS libraries are crap but then you like clones of Angular, React, etc but in a different language? You don't have to like JS, but it seems to me that you answered your own question: "Mind naming some great libraries?"
      - nol13 10y ago
        It's also really easy to get a package on npm.

Not according to the millions of people who use and like JavaScript.

by Touche 10y ago

Not according to the millions of people who use and like JavaScript.

rubber_duck 10y ago

The quality of JS ecosystem speaks for itself.

untog 10y ago
The breadth of the JS ecosystem speaks for itself, too.
- rubber_duck 10y ago
  Absolutely - multiple halfassed re-implementations of the same thing found in most languages std lib is a huge reason why the language is bad (remember the left pad fiasco ?), but the semantics of the language make it fundamentally flawed without breaking backcompat. JS ecosystem is actually quite bad when it comes to functionality - but they do have 10 versions of same thing for stuff they do have and each of those works only in specific scenario it was written in but nobody bothers to extend it and writes their own instead when they need to solve something similar because reading other's people JS is a nightmare. If anything the kind of breadth JS ecosystem has shows just how hard to maintain other people code is.
  - rpedela 10y ago
    What a gross over-generalization. Yes there are crap libraries just like any popular language. There are also great libraries just like any popular language. If there are multiple for the same purpose, it is usually obvious which is the best one. Since you brought up the left pad thing, yes there is a small minority within the JS community that takes the Unix philosophy of "only do one thing and do it well" to an absolute extreme. But that isn't indicative of the JS ecosystem as a whole.
    - rubber_duck 10y ago
      >There are also great libraries just like any popular language. Mind naming some ? I work on Angular 2, React and TS front end in my day job - those libraries are a joke compared to similar libraries in other languages. For example Angular 2 Dart is a huge productivity improvement - having done a prototype with ng2 Dart and implemented a full app in TS having a language with sane semantics, actual standard library and a build system built by someone who knows what they are trying to do vs someone who hacked something themselves and everyone kept piling on. React compared to something like Clojure + Reagent is a similar comparison although CLJS tooling is much less mature than Dart - just dealing with immutability in JS/TS is so tedious and full of boilerplate. Just recently I had to find a library that will let me pattern match URLs and extract parameters (eg. 'foo/:a/:b(?foo=:c&bar=:d)' => {'a':..., 'b':..., 'c':..., 'd':...}) - and every option out there failed to work with anything beyond basics and the implementations were horrible - and this is JS core competency.
      - rpedela 10y ago
        You are claiming that JS libraries are crap but then you like clones of Angular, React, etc but in a different language? You don't have to like JS, but it seems to me that you answered your own question: "Mind naming some great libraries?"
    - nol13 10y ago
      It's also really easy to get a package on npm.