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 so Shopify probably also made their investors whole?
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.<p>I'd bet my money on Remix model and direction vs Nextjs
Interesting move by Shopify, given that they have Hydrogen [0]. I was half expecting Hydrogen to become its own all-purpose framework, but alas, they seem to plan for both to co-exist.<p>> While Hydrogen is focused on commerce, Remix is focused lower in the stack, and will continue to be a general web solution that scales from content through commerce and all the way to apps. Shopify will use Remix across many projects where it makes sense, and you can expect to see more of our developer platform with first-class Remix support over time.<p>[0] <a href="https://hydrogen.shopify.dev" rel="nofollow">https://hydrogen.shopify.dev</a>
I don't understand what is the business case for acquiring an open-source framework?<p>Can someone explain why couldn't they just contribute or fork the project?
I'm not sure how to feel about this, but my main wish for Remix is a public roadmap and full development in the open. There is overlap but also healthy competition between it and NextJS, and I'm really interested to see where Remix goes next.
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.<p>I know from prior use of React Router, the maintainers love the big rewrites between major version numbers.
Is this really a good thing though? Sounds a bit more like a soft landing than a success story. I am not sure this is in the interest for the framework either. Michael and Ryan will stay for two years until their lockin is over and then resign and start building the next thing (a good thing).
the <a href="https://remix.run" rel="nofollow">https://remix.run</a> website is beautifully fun. I know lots of people will berate it for being OTT, but scrolling I wouldn't say is a critical path given the docs/get-started call to actions.<p>I'd be interested to see what Shopify do with remix, are they more interested in the core team, maintaining remix.run as they plan to/do(?) use it internally. I assume they want to offer this framework as a baked in enhancement of Hydrogen[1] to try and help clients build more robust sites.<p>1: <a href="https://hydrogen.shopify.dev" rel="nofollow">https://hydrogen.shopify.dev</a>
I have strange feeling about these nodejs server based and the direction of the web and the chaotic of Big|VC-backed corps playing chess. And that also causes effect on web job market. .. what's your retirement plan?
This post is puzzling:<p>1. Michael Jackson tags himself as "Co-founder, CEO."<p>2. Remix website gives no indication that it's a company or that there is a company called "Remix."<p>What's going on here? What exactly what "acquired?"
Is it me or is Remix sort of a weird, and slightly sketchy flip of the OSS money making pipe? I understand that people can take open source projects and turn a business around them by providing hosting (Vercel/Next for example), but having people 'invest' in an open source framework just seems fundamentally wrong. What is the payout for those investors, what have Shopify actually given (and to whom) for what it has 'aquired' here? Also what of the $3m Remix 'raised' last October, where has that gone, what did those people get in return? I just fail to see where the return is on all of this...
I've settled on using Java for backends since it's just so robust and performant. But damn if this new round of TS-enabled frameworks (Remix, Next, SvelteKit, QwikCity etc) isn't compelling with their full-stack type safety and easy development. Using same component-oriented vocabulary to seamlessly switch between and even combine client and server rendering, and co-locating client code with data loading all in TS with end to end type safety, is hard to beat. Makes me worry about being left out with non-TS backend like Java. Interested to see how this develops.
Why acquire something that is MIT licensed?<p>Is this really just a talent acquisition?<p><a href="https://github.com/remix-run/remix" rel="nofollow">https://github.com/remix-run/remix</a>
Congrats to the Remix team.<p>I'm not entirely sure how you acquire a web framework or what the end-goal is, but I'm sure smarter people than I have the done maths.
Remix is wonderful.<p>Combined with CloudFront, you can save a lot of money compared to Vercel when you become moderately successful.<p>(yes, you'd need to be comfortable rolling your own to some degree, for some things, but honestly the value is huge)
We're having massive issues with Shopify at the moment. They decided that for us to integrate with them, we HAVE TO use Shopify's billing system. We had been using them with an unlisted app for a long time and our mutual customers loved it.<p>Recently Shopify decided to cut off our unlisted app (or whatever they call it) so that our users can no longer connect to Shopify. The only way we can get verified is to use their billing (we're using Stripe).
Having built a number of headless Shopify sites in Next JS this is slightly concerning, I was imagining a port over to Hydrogen at some later date with minimal changes rather than a total replatform.<p>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.
As someone who started off in Ember and then began developing in React: I've never liked React Router. IMO, the url is best treated as data because it doesn't work well as part of the presentation layer.<p>The interesting part (for me) is that I'm pretty locked into React because of Shopify's Polaris project.
Aren't Remix and Hydrogen supposed to fill the same role ? Despite what Remix's creators try to argue, for me Remix is great for low interactivity website like e-commerce website, even doing a simple client-side request without refresh is a pain in Remix
This is likely a better link: <a href="https://shopify.engineering/remix-joins-shopify" rel="nofollow">https://shopify.engineering/remix-joins-shopify</a>
~No they aren't rebuilding Hydrogen in Remix.~
Edit: Spoke too soon on the above, sorry.<p>Remix raised funding. Ran out of money with no scope to self sustain or raise money. They downsized (see Kent Dodds. Perhaps there are others). Strong engineers that built the platform got acquihired.
There seems to be a disconnect between what Shopify do internally and what they ask of their users. With Hydrogen and now Remix you would think they have their sh*t together. But when the official docs recommend that you inline jquery click handlers for a simple adjustment to their shop, I just don't know what to think.<p>All in all the Shopify dev experience for me is on par with Wordpress. I hold my nose and cash the cheques. Then hurriedly leave the premises in a long trench coat with my hat pulled down to avoid being recognised.