3 ms·

That's a bit like looking at the source code for Linux's TCP stack and saying "All that work just to make a TCP connection? I'm definitely not using Linux". If

That's a bit like looking at the source code for Linux's TCP stack and saying "All that work just to make a TCP connection? I'm definitely not using Linux". If all you want is a select in React, you can just do `<select><option value="A">A</option><option value="B"></option></select>`. The tutorial is showing how to roll your own select-like control using divs. I doubt that it is much easier to do that using any other JS framework.

pothibo 10y ago
Are you really comparing the linux TCP stack with an HTML select tag and justifying React through that comparison? Are you for real?
- TheCoelacanth 10y ago
  No, I'm saying that implementing something is usually harder than using something. The tutorial is about how to implement a select; not about how to use a select.
  - pothibo 10y ago
    That's still wrong. Using a <select> is still much easier than using React's implementation of it.
    - artimaeis 10y ago
      > Using a <select> is still much easier than using React's implementation of it. Yes, of course it is. But reading a tutorial about how you could implement something so understandable as <select> using React is a pretty good guide to understanding React! At least, to me it seems pretty great.
lhorie 10y ago
I think there's something to be said about this being analogous to a language whose homepage example is starting an http server, vs one whose first example is merely fibonacci but using pattern matching (or whatever tickles your fancy). If "enlightenment" is realizing you can use React to reinvent [insert-library-here], then what's so special about it? Any half-decent framework can do that. I think the argument about composability and scalability (which imho are the real value-add that React brings over e.g. jQuery) is a bit lost in that example because it spends so much time on stuff that looks rather pointless and mundane.

pothibo 10y ago

Are you really comparing the linux TCP stack with an HTML select tag and justifying React through that comparison? Are you for real?

TheCoelacanth 10y ago
No, I'm saying that implementing something is usually harder than using something. The tutorial is about how to implement a select; not about how to use a select.
- pothibo 10y ago
  That's still wrong. Using a <select> is still much easier than using React's implementation of it.
  - artimaeis 10y ago
    > Using a <select> is still much easier than using React's implementation of it. Yes, of course it is. But reading a tutorial about how you could implement something so understandable as <select> using React is a pretty good guide to understanding React! At least, to me it seems pretty great.

lhorie 10y ago

I think there's something to be said about this being analogous to a language whose homepage example is starting an http server, vs one whose first example is merely fibonacci but using pattern matching (or whatever tickles your fancy). If "enlightenment" is realizing you can use React to reinvent [insert-library-here], then what's so special about it? Any half-decent framework can do that. I think the argument about composability and scalability (which imho are the real value-add that React brings over e.g. jQuery) is a bit lost in that example because it spends so much time on stuff that looks rather pointless and mundane.