Just recorded this little performance
demo of @overtone_app while working on my talk for @localfirstconf.
Near-zero query latency enables a magical UX.
I highly recommend using a helper function like `shouldNeverHappen` instead of throwing errors directly in your code (only applies to defects/panics).
It's an easy way to make your code more readable and improve DX by automatically opening the debugger during dev.
Just recorded this little performance
demo of @overtone_app while working on my talk for @localfirstconf.
Near-zero query latency enables a magical UX.
After 4 years of work, I'm incredibly excited to introduce LiveStore, the next-gen data layer I'm building for Overtone.
It's based on reactive SQLite and has a built-in sync engine. Give it a try - would love your feedback!
🔮 GraphQL prediction for 2019: Resolver-first server frameworks will begin to replace the currently popular schema-first approach.
Main reasons:
◆ No code redundancy (i.e. single definition of resolvers and types)
◆ Better code reuse & type-safety
◆ Superior DX
After many recommendations, I finally switched from VSC to @cursor_ai and ... wow!
It's absolutely incredible. If you like Copilot (or if you don't), you'll be blown away by Cursor.
There is no going back. 🤯
🤯 Just tried out the upcoming Next.js version (via canary) together with Prisma 2 for type-safe DB access within (!) your React component. Safely. This tech stack feels like a huge leap forward! Expect a demo soon!
🤦♀️ Every time I'm hearing "GraphQL is overkill" I remember the times when people said "React is overkill". Sure it is something you have to initially learn but once you're familiar with it, it's literally the easiest way to build a good API.