4 ms·

I suspect that OP is indirectly if not casually admitting that react core is bad or terrible DX. Can we discuss technicalities of our decisions and not just shi

I suspect that OP is indirectly if not casually admitting that react core is bad or terrible DX. Can we discuss technicalities of our decisions and not just shill react frameworks? That thread is just a niagra of nonsense. The most impressive thing is how much OP mentions the most obvious things with such great profundity. "Gib ssr, gib routing..." thanks man. We can't read docs or landing pages it seems.

jbergens 4y ago
I think the discussion comes from the view that React has not had any server side framework and that may be very useful. A lot of the comments fail to differ between client side and server side tech. Meta was probably using php for their backend and didn't need any server side part, hence 3rd party frameworks like NextJs and Remix. I've seen companies use .Net or other languages on the backend also, they are also less interested in a React server side solution but if it does not stop other server solutions from being used it may not hinder much either.
PaulHoule 4y ago
The one reason I am still interested in React for my side projects is that react-three-fiber exists. So far I have avoided using competitive frameworks because I use React at work and really mastering it makes me more productive globally than being a dilettante at Vue or Svelte. Lately though I have been using htmlx which doesn’t address all the problems that React does, particularly highly complex applications where an update can change other components on the page. It is easy though, when classifying things, to have a list of the 5 Last things so if the mouse clicks twice I can change the select and it posts to the server. I have a few htmlx features bolted on top of a system which otherwise would look like a web app from 1999…. And I can say boy is it fast.

4 ms·

I suspect that OP is indirectly if not casually admitting that react core is bad or terrible DX. Can we discuss technicalities of our decisions and not just shi

by vagrantJin 4y ago

jbergens 4y ago
I think the discussion comes from the view that React has not had any server side framework and that may be very useful. A lot of the comments fail to differ between client side and server side tech. Meta was probably using php for their backend and didn't need any server side part, hence 3rd party frameworks like NextJs and Remix. I've seen companies use .Net or other languages on the backend also, they are also less interested in a React server side solution but if it does not stop other server solutions from being used it may not hinder much either.
PaulHoule 4y ago
The one reason I am still interested in React for my side projects is that react-three-fiber exists. So far I have avoided using competitive frameworks because I use React at work and really mastering it makes me more productive globally than being a dilettante at Vue or Svelte. Lately though I have been using htmlx which doesn’t address all the problems that React does, particularly highly complex applications where an update can change other components on the page. It is easy though, when classifying things, to have a list of the 5 Last things so if the mouse clicks twice I can change the select and it posts to the server. I have a few htmlx features bolted on top of a system which otherwise would look like a web app from 1999…. And I can say boy is it fast.