The article is cringe yolo for sure With that said I was planning to use prisma and went and looked at issues on GitHub. They’re egregious … and I will not be

The article is cringe yolo for sure With that said I was planning to use prisma and went and looked at issues on GitHub. They’re egregious … and I will not be using prisma The library also looks like it was written in a yolo way as well. My guess is the graphql background has permanently stunted it, as the project manager keeps wanting examples for performance issues instead of realizing the entire fact joins are missing to begin with is idiotic and absurd. So my guess is they’re piecemeal fixing one off issues instead of fixing the problem at its root, probably because prisma code is not designed with that in mind from the beginning