4 ms·
For my money there isn't a better tool than Prisma right now. It's a truly fantastic database experience. It's significantly better than TypeORM and/or Knex, an
by stevebmark 3y ago
For my money there isn't a better tool than Prisma right now. It's a truly fantastic database experience. It's significantly better than TypeORM and/or Knex, and of course better than the unfiltered nightmare of ActiveRecord. SQLc for Golang isn't a great library, but it has the right overall idea: stay close to SQL while still getting language typings, and codegen. I think everyone should learn from the Prisma developer experience, it's the best of all worlds: static typing, codegen, seamless database interface, while still having as much granular control as you want.
- rlili 3y agoI agree. However, a tool like Prisma only seems possible (with all its benefits) within Typescript, which is able to compute arbitrary types dynamically.
- stevebmark 3y agoI don't entirely follow, because the Prisma client is static code generated from your database schema. There's nothing dynamic about it, unless you're referring to generics?
- Glench 3y ago> unfiltered nightmare of ActiveRecord Huh, I've only heard good things about ActiveRecord. Care to elaborate?
- stevebmark 3y agoThe entire article is about problems with ActiveRecord.
- fellowniusmonk 3y agoEven at a cursory glance some of the things they suggest as the solution like being "migration first" is exactly in alignment with ActiveRecord, which has always been migration first. Even the | based syntax they post functions similarly to AR . chaining. This person is clearly writing from a problems with python's ORM perspective. I am very happy with AR, I have spent a lot of time in data engineering as well and I find raw SQL perfectly fine and expressive for reporting, and data query though I understand why many don't get or like it, etc. ORM's really shouldn't be used outside OO app dev but for application mapping AR is great and I'm incredibly happy with it's ergonomics and dev friendliness, quite frankly for SQL naive app devs I would much rather they use it because it tends to optimize SQL queries better than your typical app dev with lower-mid tier sql experience. SQL is basically a functional language (saying that ticks a lot of people off but it's true) though which is why many devs hate it as it requires you think functionally. The only thing I think is an actual improvement recently in the space in terms of writing queries is what DuckDB has done.
- DangitBobby 3y agoPrisma is pretty good, but I'm hoping they pay attention to migrations soon and reverse the decision not to use transactions in migrations.