Did you know that with a single command, you can obtain a JSON representation of your #Swift app's internals and size? You can also push it upstream to gain insights over time. Check it out here: docs.tuist.dev/en/guides/d... 
We're kicking off our open source fellowship program by sponsoring @schickling.dev from @livestore.dev
It might seem surprising to sponsor LS as it is a data layer that brings data closer to the UI, traditionally a server's job, and we're a server-first framework.
More: rwsdk.com/blog/rwsdk-x... We're insanely excited! Cannot wait to see what the future of web-development holds:
rwsdk.com/blog/rwsdk-x... 
Very excited to announce that I'll partner with @redwoodjs.com over the coming months to improve Cloudflare worker support for @livestore.dev 
Check out our article that explains how you can ensure that no traffic spike overwhelms your DB and hurts your business!
pris.ly/black-frida... What does Black Friday have to do with connection pooling?
🏪 Your online shop is built on serverless.
🏔️ On Black Friday, traffic peaks!
👉 Lots of requests, lots of DB connections, limit reached.
😵 Your DB can't serve new requests.
💸 You're losing cash!
How to avoid this? 
Back in the city
Thank you so much! Another session on Friday 😁
when a developer has to market anything they’ve made.
#ZedEditor Download Zed and view the full changelog here:
zed.dev/releases/sta... The Zed agent panel has received some extra polish: - Mistral tool-calling support - Improved UX for editing previous messages - Improved UX for dismissing an edit to a previous message - Improved responsiveness of mouse interactions with the agent panel
Icons now appear next to files and folders when Zed is configured to use its custom picker instead of the system-provided dialogs for `Open` and `Save As` operations ( `"use_system_path_prompts": false`).
🚀 Zed v0.188 is out! Zed can now parse and load host names from the SSH config. To disable this behavior, use `"read_ssh_config": false` in your `settings.json` file.
Scaffold your database with just a few prompts, right inside @vscode.dev.
In this video, we use the Copilot Agent via the Prisma extension to:
✅ Generate a schema
✅ Define models + relations
✅ Migrate to a fresh Prisma Postgres DB
Check it out 👇
pris.ly/yt/copilot-ppg 
Help us explore the current state of continuous integration in Apple development and how it can be enhanced:
community.tuist.dev/t/whats-you... 📚 When v7 comes, we'll share comprehensive upgrade documentation so that you're well equipped for this change.
In the meantime, check out our blog post going into this topic in even more details!
pris.ly/output-article 🤨 In essence: things that worked fine in `node_modules` suddenly broke.
If you saw this warning, added an `output` path and saw errors due to that, we recommend that you simply revert to generating into `node_modules` for the time being. 🚨 But many developers hit issues after switching to a custom `output` path.
Some saw linting errors in the generated code, which broke their dev servers (because lint errors block startup).
Others ran into bundling problems, path resolution headaches, and more. 7️⃣ In the upcoming v7 major release, there'll be a breaking change: You'll need to set a custom `output` path for the generated Prisma Client instead of generating it into `node_modules`.
To help anticipate this change, we:
- added a deprecation warning
- updated our docs ⚠️ You may have seen this deprecation warning about not using a custom `output` path when using Prisma ORM lately.
We introduced this in v6.6.0 to help you prepare for a breaking change. However, the warning caused some confusion und unexpected issues.
👇 Here's what happened. 
comms from the browser company, i still like their tone and candidness. an ai-chat centric web browser to me is both horrifying and boring all at the same time, a real never-ever-do-that idea browsercompany.substack.com/p/letter-to-...