151–160 of 209 posts
Is Shopify shifting away from Rails?
We use a lot of React at Shopify on top of Rails, along with Go and Rust for critical performance systems on the backend.
Congratulations to the Remix team. Though neither Remix's nor Shopify's blog posts make it clear, I'm guessing Michael and Ryan will continue to lead Remix development while hopefully having a team of focused engineers working with them. Since Shopify really believes in and wants to use the tech, it's great that they'll be able to pay engineers to continue to develop it in the open. I believe Remix also was VC funded…
happy noises from JJ who led their seed https://twitter.com/josephjacks_/status/1587136935981481984?...
Wow and their (OSS Capital) first exit since founding in 2018. Talk about patience, but well worth it I'm sure!
Of course a replatform wouldn't be necessary if Shopify would help out by - for example - not force logging out (and otherwise breaking checkout) for users that came from a headless store.
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.
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…
> the all in one framework that does it all out the box Wouldn't Angular and Vue count as cohesive "batteries included" frameworks? Having to work on your own build setup feels very inane.
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.
Earlier quoted context omitted.
We're working on a new version of Hydrogen which is powered by Remix: https://hydrogen.shopify.dev/roadmap/ It's nice to not have to build two meta-frameworks (along with docs and support) so Hydrogen can focus on commerce things.
Will there be beta releases before Feb? I'm looking to kick off some headless shopify projects soon - and ideally I don't have to rewrite them in a few months time.
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.
framework vs library -- how would you define them?