Well yeah… why else would the company have bought them? It wasn’t because they just love ORMs and this one specifically they just wanted to make sure survived because they happened to be using it. It doesn’t work like that.
You can mostly just skip past whatever vague platitudes the announcement post makes toward stuff like this and instead just watch the product closely over the next few months to figure out how it’s gonna go. Trusting anything said in the announcement is a recipe for getting burned later
I think many saw this coming and it's probably a good thing. Personally I went with Kysely as a thinner abstraction with less risk of being acquired and turned into something that no longer aligns with my objectives. Still this is probably a nice boost to the major rewrite the Drizzle team is working on.
I use Sequelize at work and have used drizzle for a few personal projects and I can say that I really like the following:
- Native TS integration
- The migrations system is wonderful
- The API is more intuitive, imo.
I think it comes down to personal preference to use any/none of these tools, but I liked it enough to donate some space cash to the project.
I don’t use this specific orm but orms in general are trying to solve a very hard problem and as such there are a lot of ways to mess it up. If you can be the least bad at it and create slightly less dumpster fires than everyone else that’s a huge thing
I am sure there are ways the Drizzle and PlanetScale will be able to integrate. If we do it will all being using open specs and standards so other database providers can leverage the same features.
In terms of expanding to other languages, this has not been discussed but never say never I guess.
Well deserved for the drizzle team but difficult to imagine a world where they don’t prioritize Planetscale-specific work.
Well yeah… why else would the company have bought them? It wasn’t because they just love ORMs and this one specifically they just wanted to make sure survived because they happened to be using it. It doesn’t work like that.
You can mostly just skip past whatever vague platitudes the announcement post makes toward stuff like this and instead just watch the product closely over the next few months to figure out how it’s gonna go. Trusting anything said in the announcement is a recipe for getting burned later
This is fantastic. The Drizzle team works incredibly hard and they absolutely deserve this. This feels like quite the pair
I think many saw this coming and it's probably a good thing. Personally I went with Kysely as a thinner abstraction with less risk of being acquired and turned into something that no longer aligns with my objectives. Still this is probably a nice boost to the major rewrite the Drizzle team is working on.
Can someone non-drizzle or planetscale explain to me the appeal of drizzle while other orms/sdks already exist?
I use Sequelize at work and have used drizzle for a few personal projects and I can say that I really like the following: - Native TS integration - The migrations system is wonderful - The API is more intuitive, imo. I think it comes down to personal preference to use any/none of these tools, but I liked it enough to donate some space cash to the project.
I don’t use this specific orm but orms in general are trying to solve a very hard problem and as such there are a lot of ways to mess it up. If you can be the least bad at it and create slightly less dumpster fires than everyone else that’s a huge thing
Huge for drizzle! The DX they have is amazing!
We are so excited to be working with the incredible Drizzle team! I am around to answer questions if anyone has any.
Hey Sam, love your tweets. Have a couple of questions:
- What kind of Drizzle x Planetscale specific integrations can we expect to see?
- Is Drizzle considering expanding from Typescript to other languages like Python? (which has very poor database drivers).
Thanks
Hi Pedro,
I am sure there are ways the Drizzle and PlanetScale will be able to integrate. If we do it will all being using open specs and standards so other database providers can leverage the same features.
In terms of expanding to other languages, this has not been discussed but never say never I guess.
Well deserved! this is a huge win for TS backend stack