@SuiInsiders It's easier for $BTC to get to $300k than $SUI to get to $10
English
CaptEze
973 posts
CaptEze
@Capt_Eze
Software Engineer || Crypto || Business guy || Quantum computing
Port Harcourt, Nigeria Katılım Mayıs 2023
215 Takip Edilen147 Takipçiler
Which of these happens first? 👀🚀
$BTC: $150,000
$SUI: $10
$ETH: $10,000
$SOL: $500
$BNB: $2,000
$XRP: $10
$LINK: $100
$HYPE: $100
$AVAX: $150
$DOGE: $1
$ADA: $3
$ONDO: $10
$APT: $50
$RENDER: $50
$HBAR: $1
Bullish on $SUI 💧
English
Updates on this @ankur_datta_007 .
We considered a lot of weights and just switched back to primsa-generator-js.
Currently, the generation emits pure js and we have no worries.
CaptEze@Capt_Eze
Updates @ankur_datta_007. Ton of non compatible fields from Prisma v7 on Prisma next. And I see a lot of breaking changes from queries patterns to the type system. The migration would require a ton of changes and careful updates - the codebase is large. I'll sync in with my team and know the way forward.
English
use this example to see how to use it in your apps
pris.ly/postgis-example
and if you want to close out a long standing prisma orm feature request, @william_ma14406 and team has made it *increeeeeedibly easy* to contribute/build your own extension 🧵
English
CaptEze retweetledi
Prisma Next (soon Prisma 8) already supports geospatial queries 🗺️
PostGIS has been one of the most requested features I’ve seen over the past three years, so I built the extension myself.
Link to example in the 🧵
CaptEze@Capt_Eze
Guess what. @prisma next has support for vector and geometry extension.
English
And they call it "locking in"
Alex Hormozi@AlexHormozi
People used to waste their time doing shit that didn’t matter. Now they are vibe coding shit that doesn’t matter.
English
CaptEze retweetledi
People used to waste their time doing shit that didn’t matter. Now they are vibe coding shit that doesn’t matter.
English
CaptEze retweetledi
Dear entrepreneurs,
Please, in the name of all that is holy, stop sending these generic AI-generated proposals.
Why?
They are often too text-heavy.
They lack human imperfection, which coincidentally lets the recipient know that you actually worked on the document.
And worse, they all have the same “Claude-design” standard look.
Don't get me wrong: Use AI to build your proposal, synthesise your thoughts or test your ideas. Of course.
But this slapstick, cut-and-paste, copious MBA-lingo, text-heavy stuff is not it.
Focus on the single simple core idea.
Personalise the design.
Reduce the text.
Make it your own.
Honestly, no one is going to spend 30 minutes reading a 28-page generic document littered with em dashes.
Opening attachments has turned into an extreme sport.
Phew!
Ok… Ngibulaleni ke!
VT
English
Updates @ankur_datta_007. Ton of non compatible fields from Prisma v7 on Prisma next.
And I see a lot of breaking changes from queries patterns to the type system.
The migration would require a ton of changes and careful updates - the codebase is large.
I'll sync in with my team and know the way forward.
Ankur Datta@ankur_datta_007
@Capt_Eze @prisma you should start upgrading then, and also lmk how it goes!
English
Guess what.
@prisma next has support for vector and geometry extension.
CaptEze@Capt_Eze
GM guys. I need experience based responses. What is the best way to handle db migrations with ORMs when you just started adding geospatial tables and relationships and the ORM doesn't support it fully, but the system is heavily dependent on the ORM. The scenario here is Postgres + PostGIS with Prisma If there are any alternatives to these, please recommend and explain
English
CaptEze retweetledi
Your users should never be the QA team.
If they tell you your API is down...
You're already late.
WatchUp tells you first.
watchup.site�
English
English
@gozkybrain4u I might not understand you clearly, but this seems similar to saying "HTTP is a superior API".
English
We migrated from a layered architecture to a modular setup.
Upgraded from Prisma v6 to v7.
On v7, we keep the generated files inside our source directory.
Pros - runtime is over 80% better, and the codebase is easier to manage, queries are faster and more deterministic
Cons - Ram Usage spike on code editors.
Even ts native (both preview and stable) didn't do significantly better
English
English
English
@theTechPriest_ @prisma Omor.
Maybe Prisma is just doing what it's supposed to do.
My db is really big.
English
English
@ankur_datta_007 @prisma Wow..
I'd definitely try it out tonight.
I'm on v7
English
@Capt_Eze @prisma also which version are you using? I'd give Prisma Next ( soon Prisma 8 ) a try, as we've made several performance improvements to it.
pris.ly/pn-performance
English
@ankur_datta_007 @prisma Thanks man
I actually applied this optimization about 2 weeks ago. I got about 20% lesser worries.
But for it's still an issue for my team
English
@Capt_Eze @prisma here's a quick tip that can help improve intellisense performance.
prisma.io/docs/orm/more/…
English