31–40 of 209 posts
we buyin frameworks now
Anyone remembers that upon Remix' initial release, one had to buy a licence for 250 USD? https://web.archive.org/web/20201204025307/https://remix.run...
I don't understand what is the business case for acquiring an open-source framework? Can someone explain why couldn't they just contribute or fork the project?
It's in Shopify's best interest to maintain that developer love and Remix can help with that. Here are two hypothetical situations to highlight that point:
1. If someone else, say, Swell [1], had better DX than Shopify, we would see Shopify start to lose market share to Swell for the segment of the market where developers can influence the tooling decision (i.e. agencies).
2. If in two years from now, everyone is using Next.js to build e-commerce sites, that would put Vercel (the company behind Next.js) in a good position to promote/partner with other e-commerce providers or build their own e-commerce solution and compete with Shopify.
The developer market segment is important and DX is key there.
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. > 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…
It's nice to not have to build two meta-frameworks (along with docs and support) so Hydrogen can focus on commerce things.
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. All in all the Shopify dev experience for me is on par with Wordpress. I hold my nose and cash the…
There's often a disconnect between the technical staff who write customer-facing documentation vs the backend engineering teams. Often the technical writers will be working closely with real customers. The customers will come to them 90% of the time with hacky custom jQuery stores + the support staff won't be highly skilled Front-end engineers (usually a junior-dev grasp of JS/web dev).
I know from prior use of React Router, the maintainers love the big rewrites between major version numbers.
I'd bet my money on Remix model and direction vs Nextjs
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. All in all the Shopify dev experience for me is on par with Wordpress. I hold my nose and cash the…
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.
React Router -> Remix
Redux -> RSC
Snowpack -> Astro
"This time, we will make it right" kind of feeling.