Live data from Hacker News

Viewing profile — sachinraja

sachinraja

HN member
Joined
Fri, May 06, 2022, 9:30 PM UTC
HN karma
10
Public activity
14 items

About sachinraja

https://twitter.com/s4chinraja https://github.com/sachinraja

email: s@sachinraja.com

Recent public activity

  1. comment
    Comment #32085329

    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. comment
    Comment #31970039

    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 enj…

  3. comment
    Comment #31970013

    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. comment
    Comment #31969973

    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/…

  5. comment
    Comment #31969957

    Vite could use swc for compiling in the future.

  6. comment
    Comment #31969941

    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 ca…

  7. comment
    Comment #31960668

    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 bec…

  8. comment
    Comment #31291158

    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…

  9. comment
    Comment #31290798

    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 …

  10. comment
    Comment #31290715

    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. comment
    Comment #31290691

    Thanks for clarifying!

  12. comment
    Comment #31290066

    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 don…

  13. comment
    Comment #31289974

    Could you elaborate on this? What part of tRPC do you think is unsound due to the type system?

  14. comment
    Comment #31289945

    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 fr…