3 ms·

> Deno fixes both of those problems with a proper permission model and a standard library Bun has a better standard library than Deno. You get a DB driver, S3

• spartanatreyu 11mo ago
  > Bun has a better standard library than Deno. You get a DB driver, S3 client, etc which on Deno are all third party deps. Aren't you hosting Bun on a 3rd party host though? Wouldn't you want to use the 3rd party's own dependency to connect to the 3rd party's services? --- I wasn't sure how bun handled it's db driver so I just checked the docs. Looks like they try to have a single api for multiple databases by writing queries in template strings. I can see the appeal of a single api, but using template strings looks like a bad way to do it. What happens when someone adds a keyword or function into a query that exists in one database engine but not another? Or even in one version of a database but not another? Or even in the same database engine and same version but with different settings? It's a terrible debugging experience trying to resolve those kinds of issues when you're depending on a database that someone else has set up. You need a different driver for each database engine, or you can have a unified api if you use an ORM since it can translate or shim your query into the SQL supported by your database engine.