sachinraja

5 ms·

1.
by sachinraja 4y ago
Vite is not built in Go, esbuild is. esbuild is not the only reason why it's fast either, see https://vitejs.dev/guide/why.html .
2.
by sachinraja 4y ago
If anything, Vite is less complexity. It's much easier to use and configure than any other build tool I've used. If you don't have a need/want for Vite, that's fine, but others enjoy using it. I am not fretting over
3.
by sachinraja 4y ago
If they don't have knowledge of the frontend build world, then maybe they'll have to do a bit more reading. Who should Vite's landing page target?
4.
by sachinraja 4y ago
Vite does not throw out any experience. It builds upon Rollup, esbuild, and other existing tools. There's a great page on how it's cutting edge here: https://main.vitejs.dev/guide/why.html . I suggest you try
5.
by sachinraja 4y ago
Vite could use swc for compiling in the future.
6.
by sachinraja 4y ago
I don't think anyone is expecting an existing production project to switch over. Vite offers amazing DX for new projects though. Just because something is solved doesn't mean it can't get better.
7.
by sachinraja 4y ago
How is React not solving essential problems? Suspense solves a pretty essential issue. Also Svelte can quickly increase in bundle size and if you have enough components, it can become bigger than the equivalent in other frameworks: https:&
8.
by sachinraja 4y ago
Using TS type inference to its fullest is a major part of tRPC so I don't think it has much of a benefit to you if you're ok with generation. In my experience, you can iterate more quickly without generation. I've used GraphQ
9.
by sachinraja 4y ago
You can't provide typesafety (with TypeScript) across the frontend and backend for multiple languages without codegen. There's no intention for this to be strictly JS, but there's no easy way to offer this for multiple langua
10.
by sachinraja 4y ago
It can be made to work with any framework with a proper adapter. NestJS is quite opinionated though so I suspect the two will not work well together.
11.
by sachinraja 4y ago
Thanks for clarifying!
12.
by sachinraja 4y ago
I don't believe there's anything really preventing the use of server-side events. The Websocket implementation is via an adapter and special client so I think the same could be done for SSE (probably achievable in an external pack
13.
by sachinraja 4y ago
Could you elaborate on this? What part of tRPC do you think is unsound due to the type system?
14.
by sachinraja 4y ago
tRPC offers typesafety across your frontend and backend without needing to generate any code. This makes it so updates in your backend "router" are immediately reflected in your frontend code. You can't use gRPC with TypeScri