4 ms·

One thing I prefer about Angular is all of these patterns are established and documented by the same people who designed the framework. In React they are distri

by msane 10y ago

One thing I prefer about Angular is all of these patterns are established and documented by the same people who designed the framework. In React they are distributed among hundreds of blogs and individual github repos, which all debate each other. How long has React been out? Simple patterns such as component communication are debated, and third-party documentation about them is newsworthy?

_greim_ 10y ago
The patterns handed down by the authors of Angular were one team's idea of how to do things, at a specific moment in time, which subsequently got enshrined and frozen in place for everyone for the next several years. And it works! It's a legitimate way to run a framework. But, in such an environment, there's no marketplace where ideas can compete and evolve. There's a trade-off where you have to do the hard work of navigating and choosing among competing ideas, but the benefit of React is that you can choose an architecture, today, that isn't a four-year-old snapshot of a small group's idiosyncratic architectural preferences.
- msane 10y ago
  ...the benefit of React is that you can choose an architecture... I don't see that as a benefit... you must choose, and hope you chose well, based on poorer information and docs. It's an expense and a risk. Some are more confident about the cost and risk than others, but less conscious of it I presume.
  - acemarke 10y ago
    The great thing about React is that you get to choose something that works for your team in your situation. The bad thing about React is that you need to choose something that works for your team in your situation.
    - msane 10y ago
      It takes more time and energy than the team realizes, which would otherwise be spent building the app. Its the frontend after all... what matters is UI and features. Component communication patterns and all this low level stuff is time lost.

by msane 10y ago

_greim_ 10y ago

The patterns handed down by the authors of Angular were one team's idea of how to do things, at a specific moment in time, which subsequently got enshrined and frozen in place for everyone for the next several years. And it works! It's a legitimate way to run a framework. But, in such an environment, there's no marketplace where ideas can compete and evolve. There's a trade-off where you have to do the hard work of navigating and choosing among competing ideas, but the benefit of React is that you can choose an architecture, today, that isn't a four-year-old snapshot of a small group's idiosyncratic architectural preferences.

msane 10y ago
...the benefit of React is that you can choose an architecture... I don't see that as a benefit... you must choose, and hope you chose well, based on poorer information and docs. It's an expense and a risk. Some are more confident about the cost and risk than others, but less conscious of it I presume.
- acemarke 10y ago
  The great thing about React is that you get to choose something that works for your team in your situation. The bad thing about React is that you need to choose something that works for your team in your situation.
  - msane 10y ago
    It takes more time and energy than the team realizes, which would otherwise be spent building the app. Its the frontend after all... what matters is UI and features. Component communication patterns and all this low level stuff is time lost.