3 ms·

After all this time, React's sheer tonnage of boilerplate still astonishes me. That abstraction leaks like useMemo(…) even need to exist in the first place… Fo

by ttfkam 3y ago

After all this time, React's sheer tonnage of boilerplate still astonishes me. That abstraction leaks like useMemo(…) even need to exist in the first place… Folks want to solve their own problems, but they keep getting saddled with React's as well.

CharlieDigital 3y ago
Evan You (creator of Vue) had a great quote on this: > The pain and suffering of hooks all roots from the mismatch between a dogmatic belief in the superiority of immutability and the harsh reality of the host language that is JavaScript (Feb 25, 2023) This fundamental misalignment with React and JavaScript is the billion dollar mistake.
- satvikpendem 3y ago
  Nah, I still think React made the right choice. I used to use functional languages so coming to the JS world and seeing that no lessons from that world were learned was disheartening. React, where UI = f(state), is an amazing model compared to the imperative jQuery model of before.
  - ttfkam 3y ago
    You may prefer it to jQuery's model, but that doesn't make React's model good. Try SolidJS. Similar ethos to React but far less boilerplate and performance-killing repaints. Less code is better, functional or not.
    - satvikpendem 3y ago
      Sure it does, it is good because it's functional. I could similarly write a convoluted yet highly short Perl expression, less code is not always better. I tried Solid. Signals are not new, I've used Knockout before and it turns into a spaghetti mess after a few years. I guess people today simply aren't old enough or experienced enough to know what eventually happens with fine grained reactivity.
      - dham 3y ago
        https://www.solidjs.com/guides/comparison#knockoutjs https://www.solidjs.com/guides/comparison#knockoutjs
        satvikpendem 3y ago
        That page doesn't really answer why it can solve the issues of Knockout better. Eventually the same problems will arise, of spaghetti code among things reacting to other things reacting to yet more things.

by ttfkam 3y ago

CharlieDigital 3y ago

Evan You (creator of Vue) had a great quote on this: > The pain and suffering of hooks all roots from the mismatch between a dogmatic belief in the superiority of immutability and the harsh reality of the host language that is JavaScript (Feb 25, 2023) This fundamental misalignment with React and JavaScript is the billion dollar mistake.

satvikpendem 3y ago
Nah, I still think React made the right choice. I used to use functional languages so coming to the JS world and seeing that no lessons from that world were learned was disheartening. React, where UI = f(state), is an amazing model compared to the imperative jQuery model of before.
- ttfkam 3y ago
  You may prefer it to jQuery's model, but that doesn't make React's model good. Try SolidJS. Similar ethos to React but far less boilerplate and performance-killing repaints. Less code is better, functional or not.
  - satvikpendem 3y ago
    Sure it does, it is good because it's functional. I could similarly write a convoluted yet highly short Perl expression, less code is not always better. I tried Solid. Signals are not new, I've used Knockout before and it turns into a spaghetti mess after a few years. I guess people today simply aren't old enough or experienced enough to know what eventually happens with fine grained reactivity.
    - dham 3y ago
      https://www.solidjs.com/guides/comparison#knockoutjs https://www.solidjs.com/guides/comparison#knockoutjs
      - satvikpendem 3y ago
        That page doesn't really answer why it can solve the issues of Knockout better. Eventually the same problems will arise, of spaghetti code among things reacting to other things reacting to yet more things.