3 ms·

It's sad to see a post on HN specifically devoted to Angular utterly devolve into framework flame wars. If the title were "Why Angular 2 will be better than Rea

It's sad to see a post on HN specifically devoted to Angular utterly devolve into framework flame wars. If the title were "Why Angular 2 will be better than React" I could understand, but this is just a sneak preview of features to come. Can we please just choose the tools we prefer and build stuff instead of nursing our insecurities about the choices we've made?

personZ 12y ago
As someone at the inflection point of choosing a single-page framework, I find these "flamewars" incredibly useful. Further I find the notion that this is evidence of insecurity itself evidence of insecurity -- why feel threatened that people discuss alternatives and merits/detriments? When new language features of C# or other languages (e.g. Go) are brought up on here, inevitably those features and benefits will be contrast against other languages. And they should. Because we aren't hammers and everything isn't a nail, and even if we happen to use tool A today, we usually have the capacity to move to tool B tomorrow if it made sense.
- watty 12y ago
  Surely you don't really find "off topic" complaints an insecurity. This article is about Angular 2.0, I would expect to read about thoughts/pros/cons about Angular 2.0 when reading the comments. It's similar to reading comments on a Halo (Xbox) post on Reddit. Over half the comments are flame wars about PS4 > Xbox. There have been many "framework vs. framework" potss already on HN, let's keep the flamewars contained.
  - personZ 12y ago
    What is the scope of an on-topic pros and cons discussion, though? It seems that the relative comparison should include competitors, especially given how large of a change this apparently will be. For a current user of Angular it isn't a certainty that will make them a user of 2.0.
  - joshkpeterson 12y ago
    No, sometimes you don't really know what something is without holding it up to a yardstick. Flamewars are annoying, but this isn't a flamewar. Carry on.
zghst 12y ago
I don't think this is a flame war at all, I think people are pissed at all these breaking changes. I've seen them coming from miles away, I'm still a little distant from Angular until it's API modernizes and matures. I think people like to mention React because every since it was publicized last year Facebook has had ES6 integration in mind. With Angular, 2's goals have been up for a long time but I don't think many people thought about how much the API would have to change to accommodate the new features.
rdtsc 12y ago
Reason is -- Angular 2 is quite a departure from Angular 1 and a good number of poeple will at that point might choose to envaluate other frameworks. React is the _other_ popular framework today so people are talking about. In large the discussion is fairly civil (so far), people are passionate and seem to care about the topic and are discussing it.

personZ 12y ago

As someone at the inflection point of choosing a single-page framework, I find these "flamewars" incredibly useful. Further I find the notion that this is evidence of insecurity itself evidence of insecurity -- why feel threatened that people discuss alternatives and merits/detriments? When new language features of C# or other languages (e.g. Go) are brought up on here, inevitably those features and benefits will be contrast against other languages. And they should. Because we aren't hammers and everything isn't a nail, and even if we happen to use tool A today, we usually have the capacity to move to tool B tomorrow if it made sense.

watty 12y ago
Surely you don't really find "off topic" complaints an insecurity. This article is about Angular 2.0, I would expect to read about thoughts/pros/cons about Angular 2.0 when reading the comments. It's similar to reading comments on a Halo (Xbox) post on Reddit. Over half the comments are flame wars about PS4 > Xbox. There have been many "framework vs. framework" potss already on HN, let's keep the flamewars contained.
- personZ 12y ago
  What is the scope of an on-topic pros and cons discussion, though? It seems that the relative comparison should include competitors, especially given how large of a change this apparently will be. For a current user of Angular it isn't a certainty that will make them a user of 2.0.
- joshkpeterson 12y ago
  No, sometimes you don't really know what something is without holding it up to a yardstick. Flamewars are annoying, but this isn't a flamewar. Carry on.

zghst 12y ago

I don't think this is a flame war at all, I think people are pissed at all these breaking changes. I've seen them coming from miles away, I'm still a little distant from Angular until it's API modernizes and matures. I think people like to mention React because every since it was publicized last year Facebook has had ES6 integration in mind. With Angular, 2's goals have been up for a long time but I don't think many people thought about how much the API would have to change to accommodate the new features.

rdtsc 12y ago

Reason is -- Angular 2 is quite a departure from Angular 1 and a good number of poeple will at that point might choose to envaluate other frameworks. React is the _other_ popular framework today so people are talking about. In large the discussion is fairly civil (so far), people are passionate and seem to care about the topic and are discussing it.