As an industry we very much chase trends. Very often you have to just go with the flow, or be labeled as trouble maker.

Are you referencing the Svelte docs?

Those are good points. The general sense I have is that the more typical use case for remote functions are for when you're using your own backend, hence the RPC analogy, but I could be mistaken.

Either way, there are tradeoffs to be made.

In both scenarios your web browser is making a call to a backend via a fetch request.

I would add to that, sometimes people propose solutions. First learn the goal they are trying to accomplish. They might not be fully aware of the best way to accomplish that goal.

Why are there parents around the test? My guess that has something to do with it.

I demand a full refund! 😆

Where I work now we delivery new functionality every 1-2 days, sometimes multiple times a day.

We also don't estimate our work, and it works well for everyone.

I'm trying to follow what this is. Are these components built on top of shadcn-svelte? Why does the website mention pricing?

It was a design decision. It was technically possible to support multiple components per file, but framework maintainers didn't think it as the way to go.

As someone that works with Svelte daily, I never feel limited in this regard.

Looking forward to version 2.0!

Congrats, I'm very exited to hear the news!