Comment

Comment by wokwokwok

> Remix is specifically designed to run in any JavaScript environment so that you own your stack. It is expected many —if not most— production apps will have their own server.

Mmm.

I'm know that technically remix supports static builds (1), but it feels like a bait and switch to turn a client side library into a server side framework.

Am I cynical in think perhaps there were two projects and one of them was more popular than the other (like, 2x more popular say...), so maybe if we take the unpopular package merge it to the popular one people will not notice and we can just pretend we only have one popular package?

Maybe we should just merge all the packages in npm into one package called 'all'. That would be soooo popular, great victory!

I'm joking; but taking this to the extreme makes the point; this is unabashed and unwanted bloat for people who just wanted react router; if people wanted remix, they would use remix. If you don't want to maintain two packages, don't; but this is a bit :|

> and now Remix and React Router are basically the same thing

Mm. That's not how I would describe the difference between a server side framework and a client side one.

[1] - https://remix.run/docs/en/main/guides/spa-mode

parent wokwokwok 2 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton