Live data from Hacker News

Remix web framework aquired by Shopify

remix.run

201–209 of 209 posts

Re: Remix web framework aquired by Shopify

#201
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.

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).

Re: Remix web framework aquired by Shopify

#202
post #128
post #96

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.

If you're only using React then it's just a rendering library running in YOUR application.

Re: Remix web framework aquired by Shopify

#203
post #92

Earlier quoted context omitted.

Having used both, if you already know NextJS well then I wouldn't bother switching to Remix. If you want some of the Remixy API-niceness in NextJS land then you can use tRPC (for example, there are probably other options). Nothing against Remix, I do like it, it just isn't differentiated enough from NextJS to both switching for me - yet, at least.

And what about if you've not used either framework before but would like to try one? Which one would you recommend?

For work: NextJS, because Remix's future is now a little less clear. Also, there's 10x the help and documentation for NextJS. NextJS is where the mindshare is, for better or worse.

For fun: Whichever appeals to you :)

Re: Remix web framework aquired by Shopify

#204

Earlier quoted context omitted.

> i get the good intrnt to make pages fast, but making thin client pages like this radically reduces the general utility & agency of the web. I'm not sure what you mean by this. Remix and related technologies don't limit what you can do on the client—you still have the full power of React at your fingertips. The difference is that they blur the lines between client and server such that you get more or less seamless s…

a developr can limit the power of user-agency by moving increasing amounts of power to the server. this trend amplifies developers potential. and it allows targetting "dumber" web clients. yay, good things. but it also makes the most advanced & competent web users less able & less capable. web apps have, for a while now, been fairly client-heavy, in a way that enables hacking & creativity. i'd love a strong counter-t…

the SPA era was a fluke. what we're seeing with SSR adoption in the last few years is that all the new goodies we got used to in SPA frameworks are coming back in line with the traditional web model, where i get a new document from the service after each meaningful interaction

Re: Remix web framework aquired by Shopify

#205

Earlier quoted context omitted.

FWIW: Tobi mentioned that if he had to do it all over again, he would still build the admin and business logic of Shopify in Ruby on Rails, but would probably build their liquid rendering in Rust or something like it https://twitter.com/tobi/status/1585459224506671104?s=20&t=0...

elixir/phoenix gives you a lot of the same productivity as rails with vastly higher performance. the big benefit to rails these days is the massive ecosystem of drop in gems.

Modulecounts.com shows Ruby gem output grinding to a halt. As Ruby's popularity declines a lot of gems will be unmaintained. It's a shame as I rate Ruby my favourite language after Clojure.

Re: Remix web framework aquired by Shopify

#206
post #121
post #63

Earlier quoted context omitted.

I share your feeling, but I don’t think it’s reasonable. I’ve used both now and it’s just fine as a framework. Maybe it’s in the way they present themselves.

Definitely it's how Remix presents itself. Their landing page reads like a marketing pitch by some crazy startup looking to raise money, not like a stable library to build a product on. You have to scroll quite far to get any factual information on what differentiates it from Next.js. I quote: > Focused on web standards and modern web app UX, you’re simply going to build better websites

Would NextJS's Apple-style marketing pitch at their events be more convincing to you?

Re: Remix web framework aquired by Shopify

#208

Remix is wonderful. Combined with CloudFront, you can save a lot of money compared to Vercel when you become moderately successful. (yes, you'd need to be comfortable rolling your own to some degree, for some things, but honestly the value is huge)

Can you please explain more? I thought since it is server rendered it would cost more than SSG pages served from CDNs. Can we cache pages until they are changed in a CDN?

Re: Remix web framework aquired by Shopify

#209
post #121

Earlier quoted context omitted.

Definitely it's how Remix presents itself. Their landing page reads like a marketing pitch by some crazy startup looking to raise money, not like a stable library to build a product on. You have to scroll quite far to get any factual information on what differentiates it from Next.js. I quote: > Focused on web standards and modern web app UX, you’re simply going to build better websites

Would NextJS's Apple-style marketing pitch at their events be more convincing to you?

No, I'm also not following the latest Vercel news. It feels way too corporate.
Post reply on HN