141–150 of 209 posts
Anyone currently using Remix in a production app? Read through the docs and it seems pretty interesting. Can't really get a sense for how stable it is though. I know from prior use of React Router, the maintainers love the big rewrites between major version numbers.
Earlier quoted context omitted.
Wait what? We have frameworks for frameworks now? What?? How did we get there :(
Everyone told me that Javascript ecosystem is maturing and slowing down. Everyone told me to just consider either React or Vue. But that doesn't seem to be the case.
Earlier quoted context omitted.
React is a library. Remix is a framework.
React is a framework though. The main differentiator between the two is Inversion of Control. React developers write their code to be called by the React application. You aren't choosing to include React or not (what you would do with a library), your whole frontend application is built within the context of the React environment in which it will run.
"i like to think of React as two things. React is a library. it is also an architecture (which frameworks may implement)"
Earlier quoted context omitted.
Michael and Ryan have always been about trying to make money from their React expertise. They literally created a company called React Training: https://reacttraining.com/team and have had a fairly lucrative business doing workshops for years. No harm in trying to get folks to pay for a framework. It doesn't seem it worked, but I can't fault them for trying!
Apropos of which, it always baffled me how bad the React Router documentation was, given that the company name was react-training. It was like an anti-ad.
Earlier quoted context omitted.
I was surprised how calm the remix developers reactions to the next 13 announcement were given how similar some of the new next features are. But now it makes sense! Upcoming acquisition on the horizon.
They already did some very public complaining about it several months ago when the Layouts RFC was first published.
Earlier quoted context omitted.
Wait, isn't React a js framework? Is Remix a framework over a framework?
People are using the term “metaframework” these days to describe things like Remix and Next that build on top of React as the view layer and provide many of the other bits you might need to get a fully-fledged web app up and running. Including but not limited to routing, performance optimizations for images and fonts, data fetching, SSR/static generation & regeneration
This is huge. Remix is my favorite React framework at the moment. It is by far the best abstraction I've seen of client/server model. Their API abstraction layer is just right, working with native browser and nodejs APIs, not obscure them. Typescript support is amazing. I'd bet my money on Remix model and direction vs Nextjs
Wait what? We have frameworks for frameworks now? What?? How did we get there :(
People also made fun of this "framework for a framework" paradigm. But, if it works, so be it.
Earlier quoted context omitted.
I think React is better described as a library than a framework. Frameworks for libraries sounds entirely reasonable to me.
not only reasonable but an inevitable conclusion I'd argue. I've been waiting for the current crop of React frameworks (of which Remix is my current favourite but they all bring cool thing to the table) to appear since the early days of using it - it was only a matter of time. First the library, then the patterns, then the ecosystem of add ons implementing those patterns, then the projects that scaffold sensible sets…
Wouldn't Angular and Vue count as cohesive "batteries included" frameworks?
Having to work on your own build setup feels very inane.