undefined | Better HN

Skip to content

Top Best Ask Show New Jobs

0 pointsbingohbangoh4y ago0 comments

Idk if its just me but I find the testing frameworks for expressJS to be _awful_ -- chai and mocha work great but throw in sinon and its like pulling teeth.

The lack of good documentation is painful and often treats me like I don't already know the concepts involve.

Sequelize isn't as intuitive as Django's ORM either imo.

0 comments

5 comments · 1 top-level

crucialfelix4y ago· 4 in thread

I recently set up a good old Django backend with REST framework. Frontend in Next.js

Turned out to be painfully slow to iterate. The ORM needs constant attention to join or prefetch queries.

Switched to Prisma and it's an utter joy. If the typescript has no errors then there won't be runtime errors.

Sequelize is a multi generational mess. It's a huge time waster.

> Sequelize is a multi generational mess. It's a huge time waster.

Could you elaborate on that ?

I personally like the functional aspect of sequelize.

crucialfelix4y ago

Just that there are several generations of API. This makes TypeScript pretty much useless / impossible.

Working with Prisma: if it compiles (and you don't have a business logic error), then you usually won't get any runtime sql errors.

You don't have type safety with sequelize.

saila4y ago

prefetch_related and select_related are pretty straightforward, but for more complex stuff the Django ORM can be a hindrance.

I haven’t checked out Prisma. Thanks for the tip.

crucialfelix4y ago

Sure, I always have to spend time checking logs and tuning the queries like that. By default, Django selects everything. I used to discover that joins and prefetches were hauling in large text fields when I only wanted an id or a slug.

Prisma has a great API for this, and it's easy to tune. By default is prefetches and selects related even several levels of joins deep.

j / k navigate · click thread line to collapse