Live data from Hacker News

Remix web framework aquired by Shopify

remix.run

121–130 of 209 posts

Re: Remix web framework aquired by Shopify

#121
post #63
post #34

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

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

Re: Remix web framework aquired by Shopify

#122

Earlier quoted context omitted.

So they recognize they're having problems with speed. Dropbox also spent years trying to JIT Python faster with Pyston, and were unsuccessful. They now are leveraging Rust and Go instead.

how do you keep up with developments like this? I suddenly see how interested I am in what stacks companies are using and more so what are they going to be using in the near to mid term future.

For trends:

StackOverflow Trends: https://insights.stackoverflow.com/trends?tags=ruby%2Ctypesc...

GitHub Star History: https://star-history.com/

NPM trends: https://npmtrends.com/

For specific co tech stacks:

Tech Co migrations: https://github.com/kokizzu/list-of-tech-migrations

https://stackshare.io/wikipedia/wikipedia

https://builtwith.com/

Company GitHub page

And HN in general, like surfacing this Shopify acquisition.

Re: Remix web framework aquired by Shopify

#123

Earlier quoted context omitted.

Very related: https://twitter.com/ryanflorence/status/1587096603822673920 > Seeing that Next.js 13 preview before this acquisition would have put me in major defensive mode "HEY THATS OUR API" but now I'm just super chill and can work on Remix instead of my mental health

Because they cashed out, don't care anymore $_$. Looks like Shopify's diligence team should be blamed here.

Should they be though? I'm not at all familiar with the specifics at play here, but from a company perspective, a player they can then fully shepherd to prioritize their own needs/desires for, is still a win against an alternative that would be more expensive to acquire, and which if they don't they can't own priorities for.

Obviously there would need to be a balance between determining roadmap for your own needs, and building something to more broadly appeal to use in the outside world, but getting to influence that without creating a fork is still huge.

And that's without the other considerations of the acquihire aspect.

Re: Remix web framework aquired by Shopify

#125

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. I'd bet my money on Remix model and direction vs Nextjs

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

I think React is better described as a library than a framework. Frameworks for libraries sounds entirely reasonable to me.

Re: Remix web framework aquired by Shopify

#126

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. I'd bet my money on Remix model and direction vs Nextjs

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

Have a library never depended on another or just wrapped it up nicer with helpers and stuff? You don't write ASM or C a lot anymore either right?

Many of these examples can make it easier to do things right, increasing performance by doing less things (better defaults etc) so I don't think something like this should be frowned upon.

Re: Remix web framework aquired by Shopify

#127
post #61

Earlier quoted context omitted.

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

Michael and Ryan have always been about trying to make money from their React expertise. They literally created a company called React Training: https://reacttraining.com/team and have had a fairly lucrative business doing workshops for years. No harm in trying to get folks to pay for a framework. It doesn't seem it worked, but I can't fault them for trying!

Apropos of which, it always baffled me how bad the React Router documentation was, given that the company name was react-training. It was like an anti-ad.

Re: Remix web framework aquired by Shopify

#128
post #96

Earlier quoted context omitted.

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

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.

Re: Remix web framework aquired by Shopify

#129

Earlier quoted context omitted.

I get the purist push for Vanilla JS but for me it's still way too verbose. W3C has had decades to fix it and while it's improved it's still verbose as heck. Just implement the jQuery API into Vanilla JS and people would stop using jQuery.

"just"

Look at who makes up W3C. Then look at how much it costs to be a member.

They could afford anything if they cared to. Most of the time they don't and so the small players like Chrome get away with anything.

Re: Remix web framework aquired by Shopify

#130

Earlier quoted context omitted.

So they recognize they're having problems with speed. Dropbox also spent years trying to JIT Python faster with Pyston, and were unsuccessful. They now are leveraging Rust and Go instead.

how do you keep up with developments like this? I suddenly see how interested I am in what stacks companies are using and more so what are they going to be using in the near to mid term future.

I imagine following the tech blogs of certain companies - you can read about dropbox's engine rewrite here - https://dropbox.tech/infrastructure/rewriting-the-heart-of-o...
Post reply on HN