Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Remix web framework aquired by Shopify

remix.run

Post reply on HN
Print view View original

171–180 of 209 posts

Re: Remix web framework aquired by Shopify

#171

Post by culi »

utahthrowaway28 wrote: post #166
lirbank wrote: post #159

Also, why did Kent C Dodds leave a while ago? I mean, not the official story, but the actual one? He became a co-founder and left within a year...

I don’t know the exact details of why he left, but I can say that a lot of us were surprised and confused when he joined Remix. The other Remix founders have great reputations everywhere they’ve worked, but Kent has kind of developed into a personality cult over the years. His courses and personal brand have no doubt been very profitable for him, so I’m not too surprised to see him go back toward personal brand build…

What are some of the most common practices you've had to "deprogram"? Curious

Re: Remix web framework aquired by Shopify

#172

Post by roryokane »

Existenceblinks wrote: post #40
jacquesc wrote: post #37

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.

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” in the comment https://news.ycombinator.com/item?id=29994621 while reading discussion of a January 2022 blog post “Remix vs Next.js”.

Re: Remix web framework aquired by Shopify

#174

Post by lirbank »

utahthrowaway28 wrote: post #167
lirbank wrote: post #164

Earlier quoted context omitted.

That implies he considered Remix a failure and left. Interesting.

I doubt it. Honestly I suspect he saw more money in building content that he owned 100% based on his personal brand, whereas contributing to a project that he only owned a fraction of wasn’t up his alley.

He is a co-founder so I would believe he had more than a fraction of (unvested) stonks. A co-founder that left within a year, and prolly dropped all his shares (cliff, again my assumption).

Re: Remix web framework aquired by Shopify

#175

Post by valtism »

kylehotchkiss wrote: post #99
Toine wrote: post #34

I'll stick to NextJS. Remix seemed fishy from the very start.

To me, Remix seemed like a very lightweight reimagining of what Next excelled at (server side react with nice frontend integration). It was exciting to see how quickly it handled dynamic renders when running from a Cloudflare worker. But now that Next 13 has layouts/server components, I prefer Next.js' approach due to all the other performance work they've done with images, fonts, css, etc. One thing about Remix that…

If you want to have server-side data fetching across nested components, tying the frontend to the router is the simplest way to make that happen.

Re: Remix web framework aquired by Shopify

#176

Post by lghh »

didip wrote: post #136
ornornor wrote: post #120

Earlier quoted context omitted.

Wait what? We have frameworks for frameworks now? What?? How did we get there :(

Everyone told me that Javascript ecosystem is maturing and slowing down. Everyone told me to just consider either React or Vue. But that doesn't seem to be the case.

It seems that using Remix would indeed be just using React + server stuff.

Re: Remix web framework aquired by Shopify

#177

Post by woutr_be »

Existenceblinks wrote: post #29

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?

In what sense would this change anything to the job market or your retirement plans? Hasn't the web always gone through changes, were people had to adjust?

Software development has always been (in my opinion) an ever changing environment, where you had to adjust your skill set in order to keep up. Sure some technologies change faster than others, and it's not always the right choices being made, and maybe people jump on these new technologies rather quickly, but people innovating, and learning from failures should be a good thing.

Re: Remix web framework aquired by Shopify

#178

Post by meowtimemania »

lirbank wrote: post #159

Also, why did Kent C Dodds leave a while ago? I mean, not the official story, but the actual one? He became a co-founder and left within a year...

I noticed some negative reactions whenever Kent would publish content about Remix. I wonder if Kent+other Remix founders felt since reaction to Kent was at times negative, it'd be best for Kent to keep doing his own thing.

Re: Remix web framework aquired by Shopify

#179

Post by AprilArcus »

qudat wrote: post #160
dntrkv wrote: post #128

Earlier quoted context omitted.

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.

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

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

Re: Remix web framework aquired by Shopify

#180

Post by rickette »

solardev wrote: post #165
ornornor wrote: post #120

Earlier quoted context omitted.

Wait what? We have frameworks for frameworks now? What?? How did we get there :(

React without a framework only gives you a basic UI composition layer and some simple state management and inheritance tools. With a proper framework it becomes vastly better. It's probably a philosophical thing too. You can make your own Frankenstein site with a bunch of a separate libs or you can go with an elegantly configured and single vendor supported bolts included framework.

Meanwhile React got more love from HN while frameworks like Angular have been offering this (a batteries included complete frontend framework) for many years
Post reply on HN