Remix.run Logo
schwartzworld 3 days ago

> a single React/ShadCN button

So don't use ShadCN? It's so weird to put up this strawman app and then be like "see what's wrong with React"? Like showing two boards nailed together and being like "can you believe I needed all those power tools just to do this?"

> Add more widgets—tabs, modals, whatever—and that gap only widens

This is the benchmark I want to see. Two full-featured apps built with minimal prod dependencies. There's a pretty good chance that the various ShadCN modules share many of their dependencies so that importing more doesn't necessarily mean a linear increase in bundle size. It could be that once you build something full-featured, React projects come in smaller, or at least not big enough to invalidate the other upsides of choosing it.

9question1 3 days ago | parent | next [-]

But the OP did implement a fully featured app as the Nue comparison half of the benchmark. I have never used Nue and don't know if I ever would. I just think to be fair to the OP, even if incremental cost declines as you keep adding stuff in React, there's no way it is negative, which means the benchmark you asked for logically must have a similar result?

3 days ago | parent [-]
[deleted]
mvdtnz 3 days ago | parent | prev [-]

> Two full-featured apps built with minimal prod dependencies.

This isn't what you see in the real world. I'd rather see comparisons to real life (where 99.9% of web apps are bloated garbage) than nonsense synthetic benchmarks like that.

schwartzworld 2 days ago | parent | next [-]

Does an ecosystem like that exist for Nue? If not, it’s the only fair comparison. The ShadCN button comes with styles and behavior that wasn’t implemented in the Nue demo.

bobthepanda 3 days ago | parent | prev | next [-]

The problem is you could also just do that to Nue, there’s nothing really preventing that.

If your team or company has bad dependency hygiene, changing a single framework is not going to help you.

3 days ago | parent | prev [-]
[deleted]