Comment by altbdoor
16 days ago
I read one post before that really resonates with me, couldn't recall from where though:
You love JSX, you don't love React
Many of the jobs in my location requires React though, so I have to tolerate it somehow.
16 days ago
I read one post before that really resonates with me, couldn't recall from where though:
You love JSX, you don't love React
Many of the jobs in my location requires React though, so I have to tolerate it somehow.
There's several frameworks that use JSX but don't act like React. I definitely have found myself in the "I love JSX but don't always love React" camp. I used Cycle.JS for a while, but came back to React for the ecosystem.
For what it is worth, I'm rather proud of my smaller reactive (RxJS-based) JSX alternative (Butterfloat), which is not a Virtual DOM like React or Cycle.JS (it is more "What if Knockout but TSX?"), and I am working on its second version now (among other things expanding its SSR/SSG powers, which already have a very different, I'd argue simpler, take on SSR/SSG than the Next.js/Nuxt.js/React Server Components world).
Just found the link to the project: https://github.com/WorldMaker/butterfloat
That's neat, will give it a spin in the future.
I’m the opposite. I loved React (before its hook madness) but I hated JSX. I’ve been using a lispy language to write React since it first came out. Initially went with someone’s pet project and eventually switched to ClojureScript. If you are already tolerating a build tool to transform your code into a form browsers can run, why not switch to a better language that’s designed for nested tree structures?
Interesting to know. Personally I've also been trying out other library/frameworks, like Vue, AlpineJS, or just plain server side rendering.
I have heard a little about ClojureScript here and there. Will take a look at it when I am free!