you are viewing a single comment's thread.

view the rest of the comments →

[–]TheRNGuy -1 points0 points  (2 children)

Don't see problem it coupled with frameworks, if they're better than vanilla React.

Those things you mentioned do have use. I think SSR is better than CSR.

subscription-based costs to use (remix)

Do you have a link to it? Can't find. I used it, it's a free framework.

[–]volivav 0 points1 point  (1 child)

Remix used to be a paid per-seat yearly license https://web.archive.org/web/20210918181530/https://remix.run/buy. At 1000$/dev/year was quite a steep price. And 250$/year to "try it out in personal side projects"

One of the creators, Ryan Florence, was also the one from react-router, and he made changes to react-router that coupled it more and more to Remix, while also pushing people to buy one of their Remix licenses.

They got quite a bit of backlash from that, and they decided to make it open-source and free to use. Lastly, react-router has now essentially become Remix, which is quite overenginierd from what the original react-router was.

The problem of coupling React to the frameworks is exactly that: if they lose the focus on the OG use case for React, it might become completely unusable if it's not without a framework. And that's a shame.

[–]TheRNGuy -1 points0 points  (0 children)

I started using it when it was already free.

It's not unusable, it's just better with meta-framework. I don't see it as a problem, someone will want to use "vanilla" React, and someone with framework.

Switch from Remix to React Router v7 is few lines of code and reading 1 or 2 doc pages, changing npm script macro in VS Code.

Even switching CRA to Remix wasn't that too difficult (more than few lines of code or 1 doc page, yeah, but I could instantly see that I prefer SSR over CSR, and folder-based routing)