On: React and Remix Choose Different Futures

[codinhood]

It's kinda wild to take something people really like and just keep re-writing it while keeping the same name.

They were around when Angular 1 -> Angular 2 right? No one liked that. Angular 2 is good but calling it Angular 2 when it was so different put a bad taste in everyone's mouth.

Google did that because they wanted the Angular userbase, but that alienated a bunch devs and many decided to switch to React (me included) instead.

Seems the remix/react router team is trying to do the same. They built something popular, and they want to use that to launch their new ideas.

They want to have their cake and eat it too, a built in userbase and explore new ideas. I get it, but why not use another name so people don't get confused or frustrated?

It's just exhausting

[0xblinq → codinhood]

The reason is simple.

These guys are really, really obsessed with download counts. They brag a lot about that in twitter every time they have a chance.

What they want to reuse is the package name.

So now they launch whatever bullshit they are playing with now under the “remix” package and the next day they’ll say “look… we have N thousands downloads per second!!! We are so successful”

They did this multiple times. And will keep doing it because they are obsessed with this.

[Tade0 → codinhood]

> Google did that because they wanted the Angular userbase

I'm okay with that, because when it came out I was considered part of the Angular workforce, so I was hired to work with a framework I knew very little about at the time.

[politelemon → codinhood]

It seems angular learned from it early on because upgrades have been a quiet affair since then. React seem to be set on repeatedly learning it.

[aloha2436 → politelemon]

React itself is still the same fundamental product, not something you can say for Remix or Angular.