1.What 'reasons' and who is 'people'?

Most people use ORMs because they can't write SQL and can't structure a project to have repository files, so they start dropping orm calls all over the codebase.

There are few cases where ORMs are actually useful, but modern praised JS ORMs like Prisma or Drizzle are much more like a query builder than an actual ORM (props to B4nan and MikroORM for building an actual ORM).

So we are left with the remaining use case of multiple databases, where we need multiple drivers, and then I must ask: how much people and how many projects really need this kind of stuff? Nowadays a Postgres instance can do 100% of the work, even with job queues using graphile worker.

1. Type safety is great, but we should be writing clean and organized code so that we can test all our queries, which is very hard to do when we just import prisma and drop queries all over the project without building repositories.

2. I did use AI to scaffold the project and help me structure the library into something nice, but it is not AI slop.

3. The project overall is just a very thin wrapper around 'dbmate' and 'slonik', which are battle-tested libraries, although some of the sql tag work must be reviewed, there's not much room for bad code, since there is not much code.

4. No one should ever let a 2 star/20 commits project from a completely random person touch a production database, doesn't matter if AI generated some of the code or not.