barryhoodlum

7 ms·

1. 61.▲
   by barryhoodlum 10y ago

   And you can write a simple and clean TODO app in any framework. You really need to see how it manages complexity to evaluate it properly.
2. 62.▲
   by barryhoodlum 10y ago

   It's under 40kb gzipped. If that's a sizeable percentage of your total JS code, you probably didn't need React in the first place.
3. 63.▲
   by barryhoodlum 10y ago

   It's not a fair comparison. React is just a view layer. It's not trying to offer everything that you'd need to write a web application. React has become synonymous in some people's minds with "React + a bunch of oth
4. 64.▲
   by barryhoodlum 10y ago

   You don't "almost certainly" need Flux at all. By coincidence Dan Abramov just posted this: https://medium.com/@dan_abramov/you-might-not-need-redux-be4...
5. 65.▲
   by barryhoodlum 10y ago

   People who aren't doing complex things start using libraries that are designed to manage complex things, even though they don't need them, then complain that they're overcomplicated. Repeat ad nauseam.
6. 66.▲
   by barryhoodlum 10y ago

   The article is a bit hard to follow through Google Translate. Do these numbers mean the loss in quality is actually audible? Audiophiles can be very zealous about things that don't make much of a practical difference.
7. 67.▲
   by barryhoodlum 10y ago

   Yeah, this is exactly my first impression (I've never really looked into any past version of React Router either). Why is routing being declared in components in the first place? It seems counterintuitive. There are obvious downsides -