@sorenbs - Thanks for the clarification in https://github.com/graphcool/prisma/issues/1629 on the differences between Graphcool-Framework and Prisma.
@sorenbs @nilan - Can you please provide a priority level for changing the Graphcool Framework to use Prisma as the query engine.?
I know graphcool is evolving quickly and it can be challenging for early adopters (myself included) to keep up with the rapid proliferation of tooling/services/re-branding etc…
Some of us may be looking for a one size fits all solution, others, all the necessary building blocks for maximum flexibility.
One pain point for those who invested time (significantly on my part) in Graphcool-Framework is that we cannot immediately reap the benefits (specifically features like cascading deletes and interfaces) of Prisma/Graphcool 1.0 that were much anticipated and assumed to be coming to Graphcool-Framework. Instead, once 1.0 was reaching completion, it was announced that in order to use the features you either have to:
A. Migrate to Prisma and abandon framework (non-trivial)
B. Keep using Framework and wait until framework supports Prisma, which may or may not be a priority atm for graphcool
Without Graphcool’s hard work on all of these tools we wouldn’t be having these conversations, so thank you for that and considering this constructive feedback
I own a start-up and choose try to choose my tech wisely, and with Graphcool I see a company that we can “grow with”… so we will continue (attempt) to keep pace with you guys.