>See the link in my original post. >Over a year ago, I was investigating using Prisma to be the ORM for a GraphQL API of a Postgres database. When doing a proo

>See the link in my original post. >Over a year ago, I was investigating using Prisma to be the ORM for a GraphQL API of a Postgres database. When doing a proof-of-concept, I discovered that under the hood @prisma/client was spinning up it's own GraphQL server that it would send requests to in order to generate SQL to send to postgres. This extra middleware layer between my frontend code and postgres generated some pretty poor performing queries that took 50% longer to complete than the queries generated by using Hasura as our whole GraphQL API. Doesn't seem like it's worth writing off Node/JavaScript/NPM just due to this large project making a questionable design decision >like create-react-app, which feels the right thing to do is to spawn my $EDITOR when it sees exception in the log (which it hides) Just seems like it's Facebook's problem. I wouldn't be surprised if there's some Python package out there that does something similar. There's nothing inherent about JavaScript that makes this more likely to happen. Maybe there's something inherent about the community, but I'd really need to see a thorough empirical analysis of packages across a lot of languages before I start making judgments about that. It might be worth making fun of a particular package if they pull in way too many other packages, but it's still all a case-by-case evaluation. I personally strongly dislike JavaScript and much of its ecosystem, myself; it's just the kneejerk pattern-matching reaction that I thought was unwarranted.