4 ms·

Great news and looking forward to how this goes. I still find it incredible that the frontend javascript ecosystem hasn't found a reliable and productive conten

by lairv 4y ago

Great news and looking forward to how this goes. I still find it incredible that the frontend javascript ecosystem hasn't found a reliable and productive contender yet, a framework you could be sure would be still relevant without too much changes in 5+ years, something like what Ruby on Rails is for full-stack. Some would say that React/NextJS has this role but I have to disagree. When using React/NextJS you still have to rely on third party library for routing, state management, querying etc. like React-Query, React-Router, Redux (Next has a router but you still need libraries to do the rest). Some of these libraries change a lot, some become less relevant, new libraries emerge, and in the end when you start a React project you must go through the "library shopping" step.

rglover 4y ago
> you still have to rely on third party library for routing, state management, querying etc. Take a peek at Joystick [1]. I designed it as the exact antithesis to this. It's full-stack (Node.js back-end with a fully ssr'd component framework designed for the long-term) and doesn't introduce any special paradigms (i.e., vanilla HTML, CSS, and JavaScript—no attribute tricks/compilers needed). Everything is designed to be a fixed-API with the only changes being added functionality (i.e., no random "hey this is deprecated now" rug pulls). Philosophy is described here: https://github.com/cheatcode/joystick#what-distinguishes-joystick-from-other-frameworks https://github.com/cheatcode/joystick#what-distinguishes-joy... [1] https://github.com/cheatcode/joystick https://github.com/cheatcode/joystick
- lairv 4y ago
  Will take a look at it, and good luck with building it, such projects requires effort and test of time
  - rglover 4y ago
    Thank you, appreciate that. If you have any questions feel free to contact me directly: ryan.glover@cheatcode.co.
herrherrmann 4y ago
> When using React/NextJS you still have to rely on third party library for routing, state management, querying etc. You shouldn’t need react-router or other routing-related third-party libraries because Next’s router (and its file-based navigation system) should be enough(?). I’d also say that React itself has powerful-enough state management options (useState hook plus React context, if needed). The only annoyance I ran into was getting proper i18n working and integrated with Next (with i18next). There were some issues with Next’s newer releases and a redesigned i18n setup that broke a lot of things for me and I regretted the dependence of multiple libraries and frameworks needing to work together. (Storybook is another library that kept breaking.)

by lairv 4y ago

rglover 4y ago

> you still have to rely on third party library for routing, state management, querying etc. Take a peek at Joystick [1]. I designed it as the exact antithesis to this. It's full-stack (Node.js back-end with a fully ssr'd component framework designed for the long-term) and doesn't introduce any special paradigms (i.e., vanilla HTML, CSS, and JavaScript—no attribute tricks/compilers needed). Everything is designed to be a fixed-API with the only changes being added functionality (i.e., no random "hey this is deprecated now" rug pulls). Philosophy is described here: https://github.com/cheatcode/joystick#what-distinguishes-joystick-from-other-frameworks https://github.com/cheatcode/joystick#what-distinguishes-joy... [1] https://github.com/cheatcode/joystick https://github.com/cheatcode/joystick

lairv 4y ago
Will take a look at it, and good luck with building it, such projects requires effort and test of time
- rglover 4y ago
  Thank you, appreciate that. If you have any questions feel free to contact me directly: ryan.glover@cheatcode.co.

herrherrmann 4y ago

> When using React/NextJS you still have to rely on third party library for routing, state management, querying etc. You shouldn’t need react-router or other routing-related third-party libraries because Next’s router (and its file-based navigation system) should be enough(?). I’d also say that React itself has powerful-enough state management options (useState hook plus React context, if needed). The only annoyance I ran into was getting proper i18n working and integrated with Next (with i18next). There were some issues with Next’s newer releases and a redesigned i18n setup that broke a lot of things for me and I regretted the dependence of multiple libraries and frameworks needing to work together. (Storybook is another library that kept breaking.)