Live data from Hacker News

Remix web framework aquired by Shopify

remix.run

181–190 of 209 posts

Re: Remix web framework aquired by Shopify

#181

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.

I was curious, so I tracked down some of that public complaining:

https://web.archive.org/web/20220523220631/https://twitter.c...

HN discussion here:

https://news.ycombinator.com/item?id=31485733

Re: Remix web framework aquired by Shopify

#182
post #152
post #131

Earlier quoted context omitted.

happy noises from JJ who led their seed https://twitter.com/josephjacks_/status/1587136935981481984?...

Nice little chunk of change for him! Wow and their (OSS Capital) first exit since founding in 2018. Talk about patience, but well worth it I'm sure!

4 years doesn’t really seem like a lot of patience, or is that generally considered long?

Re: Remix web framework aquired by Shopify

#183
post #90

Earlier quoted context omitted.

Wait, isn't React a js framework? Is Remix a framework over a framework?

If we're calling both "framework" (though as another commenter mentioned, the React package is pretty much just a UI library) then you can think of React as a UI framework and Remix as an application framework. You use the React UI framework in the Remix (or NextJS) application framework.

To be a pedantic shit, I wouldn't say React is a _UI_ library. React's deal at the time of its release was 3 things:

- You can mix js and 'html' in one component

- The unidirectional 'flow' of state

- The internal model / diffing so only components that changed would update the dom

It's a mix of a library (the 'html' elements) and an architecture pattern (unidirectional flow) imo.

I'd expect a UI library to be things like buttons, windows, UI components, etc.

Re: Remix web framework aquired by Shopify

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

Re: Remix web framework aquired by Shopify

#185
post #152

Earlier quoted context omitted.

Nice little chunk of change for him! Wow and their (OSS Capital) first exit since founding in 2018. Talk about patience, but well worth it I'm sure!

4 years doesn’t really seem like a lot of patience, or is that generally considered long?

not long. generally takes 7-10 years

Re: Remix web framework aquired by Shopify

#186

Earlier quoted context omitted.

Mix feeling of this Correlation: React Router -> Remix Redux -> RSC Snowpack -> Astro "This time, we will make it right" kind of feeling.

What’s RSC? Edit – I think I found it: RSC is React Server Components. Per React’s December 2020 blog post https://reactjs.org/blog/2020/12/21/data-fetching-with-react... and June 2022 blog post https://reactjs.org/blog/2022/06/15/react-labs-what-we-have-... , the technology is still in development. Searches like “RSC JavaScript” and “RSC Redux” didn’t turn up anything. I only found the term “React Server Components”…

I hear. There's quite many kool-aid words in this area, that keeps coming up. "Island", "partial hydration", "isomorphic", without given context it's just non-sense. Even experienced developers hearing "SSR" would wonder .. wait what, why are you bringing up this obvious "server-sided rendering" .. turns out javascript folks treat it like something no one haven't ever done before. It's all confusing.

Re: Remix web framework aquired by Shopify

#187

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 '…

The remix team own the name, and npm package distribution rights. The money is used to fund development. I think you've got some good points here around the weirdness that happens when someone builds a business around something that is fundamentally open. In theory, someone could hard fork remix, rename it and do their own thing.

The moat they've built is around the specific team working on remix, the remix community, the remix name, npm distribution rights etc.

The "return" for investors will probably come in the form of selling highly integrated services (like vercel). But right now it seems to be mostly about growing remix to a critical mass. As a user, I've really enjoyed building projects with remix and I think they've built a solid community.

Good article you might find interesting: https://robertcooper.me/post/reflecting-on-remix-open-source...

Re: Remix web framework aquired by Shopify

#188
post #92

I never used Remix, why is it worth it investing in Remix?

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?

Re: Remix web framework aquired by Shopify

#189
post #160

Earlier quoted context omitted.

> React is a framework though. framework vs library -- how would you define them?

Your code calls a library; a framework calls your code.

That sounds nice but it’s not that simple. In the case of react you are doing both. You are importing functions like hooks and render. Then you pass render a function that then gets called by react.

Re: Remix web framework aquired by Shopify

#190
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.
Post reply on HN