4 ms·
This looks cool, but I just don't understand why anyone would choose to do UI components for a project like this in Next/React instead of vanilla web components
by claytongulick 3y ago
This looks cool, but I just don't understand why anyone would choose to do UI components for a project like this in Next/React instead of vanilla web components with a standard REST api, which can be used anywhere by anything.
Or, honestly, why anyone would chose to use react server components at all.
I was just kicking the tires on cal.com and saw the same thing - they did all their stuff with the react server components and next.js. And then? Well, it turns out that they needed an API, because apps do.
So they ended up reimplementing most of the logic in a RESTful API anyway.
I just SMH.
- Peer_Rich 3y agohey cofounder of cal.com here. the plan has always been to: 1. start and go fast with a mono repo and trpc fullstack api to understand and learn the fastest. once we knew what we need, we were able to build an external facing API. we wanted to be very clear to externals that using our “trpc api” is with caution due to undocumented breaking changes. a lot of companies have an internal API + external API (built later)