EdgeDB is underrated.

Graph-relational links, computed fields, constraints on arbitrary expressions, set theory-based, automated deterministic migrations via CLI, a generated TypeScript query builder instead of an ORM…

Architecture and developer experience are extremely well thought out.

EdgeDB is underrated.

Graph-relational links, computed fields, constraints on arbitrary expressions, set theory-based, automated deterministic migrations via CLI, a generated TypeScript query builder instead of an ORM…

Architecture and developer experience are extremely well thought out.

https://www.edgedb.com

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

amusement, wonder, and uncertainty
libred.org

Used it to prototype a few full-stack apps so far.

Not a backend dev by trade, but I’ve been following the project for a while.

@backpack put a bank in your pocket and use your money whenever, wherever, however without permission

icebreaker.xyz/notdevin

This sounds promising and I really like the structure at first glance. Thanks for sharing will put this in the prototype with queue 🙏🏼

Tech entrepreneur hanging out in Silicon Valley. Founder @gatsbyjs. @kylemathews on Twitter

Big refactors? Who’s “they”?

It’s PostgreSQL under the hood with custom schema modeling and query languages on top.

Well that's ambitious. Rewrite the entire db stack.

My big worry about big refactors like this is that if they do manage to get something nice working, it's missing all sorts of little features which consumes them for years and meanwhile, the rest of the industry moves past them.

It's just not possible to do it all.

That's what I'd say about traditional SQL databases. Don't even want to think about the JOIN clauses that would be involved.

In EdgeDB you can go as deep as you want. It's all handled and optimized for you.

Considering New Roles | Prev 
SushiSwap | Prev Web2 Senior Engineer/Architect | All opinions are my own

That's what I'd say about traditional SQL databases. Don't even want to think about the JOIN clauses that would be involved.

In EdgeDB you can go as deep as you want. It's all handled and optimized for you.

https://www.edgedb.com/docs/edgeql/select#subqueries

https://www.edgedb.com/docs/edgeql/insert#nested-inserts

These kinda things are great for simple crud apps but as soon as you have to do complicated/more performant queries, they fall apart

super cool learning a little about it yesterday!