3 ms·

OK, looks great but as a manager and founder of a company that is looking into sponsoring OSS, how does this make me more money?

• hu3 3y ago
  I'll bite. With tRPC, changing an attribute of a class in your backend immediately tells you what broke in the frontend in your IDE. No need to recompile or regenerate anything. Also, when developing your frontend, you'll have immediate autocomplete. Again without code generation or compilation. That alone should save you dev time and prevent a ton of frontend bugs.
  • threatofrain 3y ago
    Wouldn't optional code generation be rather desirable? Then you don't need a monorepo, which a lot of people don't do.
    • marksomnian 3y ago
      It slows down the iteration cycle - when you make a change to your API definitions you'd need to push the change to either a schema repository or into production, then regenerate the API - at which point, if you've accidentally introduced a breaking change, your frontend is already broken - you can work around this with CI that detects breaking changes, but it requires a fair amount of work. Having them in a monorepo means that breaking API changes can fail CI and never make it into production.
      • deleted 3y ago
        [deleted]