7 ms·

Meh since when is computational performance really a bottleneck? Do you find your site is loading seconds too slowly because JS is executing? I sure don't. On

• pigeons 10y ago
  Actually I do find javascript making many sites that are ultimately just displaying text, so slow as to be unusable.
  • a13n 10y ago
    How do you know it's the JS executing and not network time or the result of a poor infra decision?
    • pigeons 10y ago
      Because it works great with JS turned off, and you can measure what is using your CPU an d what it is doing and how much time it is taking (also you can measure the network).
• deleted 10y ago
  [deleted]
• leeoniya 10y ago
  > Meh since when is computational performance really a bottleneck? Ever used a phone that wasn't < 6 months old to browse the modern web? > at scale React is a front-end framework. The only "scale" that exists in its world is the fat DOM you generate and how fast it can mutate it. From that perspective, it sucks at scale (take a look at Preact and Inferno). Your iteration speed depends on good app architecture, not a specific framework. React Native does sound like a good perk, but likely isnt useful enough to make anything you cannot do anyway in HTML5.
  • a13n 10y ago
    Scale in terms of number of engineers and app size, not users
    • leeoniya 10y ago
      > number of engineers can't this be said about any popular framework? "it scales because everyone knows it" > app size what specifically makes React scale better with app size than any other properly componentized architecture?
      • a13n 10y ago
        It doesn't scale because everyone knows it. It scales because React by nature isolates business logic into components so that for the most part 100 engineers can simultaneously work on the same product and be confident they aren't breaking stuff. (Or realize they are through merge conflicts) > "properly componentized" With React, 100 engineers don't have to know how to "properly componentize" things because it's already baked into the framework. You can't really write React code without proper componentization.
        • leeoniya 10y ago
          > React by nature isolates business logic into components The essence is simply this: function MyView(model) { return template; } ...which can work with any view layer and the same 100 engineers. Especially if the model is an API with business logic around some immutable stream/state. The concept is simple enough to be described in one sentance :) > don't have to know how to "properly componentize" things I think you're overstating how difficult this problem is or forgetting that React's API must still be learned from documentation and examples.
          • a13n 10y ago
            What about state within a component? How do you encapsulate that state so that other components can't muck with it? What about passing data to that component? What about type checking that data passed in in debug mode? What about a formal API for components to talk to one another? What about knowing the explicit amount of the view tree that needs to be re-rendered based on what data changed? React has answers to all these questions and so much more. Answers that very smart people have spent years coming up with. Sure you could reinvent the wheel and build all that into your custom component framework, but then you may as well just use React.
• Bahamut 10y ago
  On mobile, it matters a lot, especially older/low-end Android phones.