neon dot com is such a cool domain name. you guys will be succesful, i can already tell. you can't lose with a domain name like that.

For most use-cases, Serverless Postgres is a nasty thing in my experience. It is way too slow and has a lot of latency over the wire, even for production apps.

The scaling requirement doesn't usually happen to startups until they hit ~4 years or later, and it is not much useful to optimize for it anytime before that. Add the cost aspect to it and it becomes close to meaningless.

You're way better off running your own managed Postgres service or container that costs about $10 a month.

Aww, man, it's started https://github.com/neondatabase-labs/neon_local_vs_code_exte...

But, be sure you don't click on that link or you'll be in violation!!11

> If you have not agreed to an Agreement or otherwise do not agree to these terms, you may not use the Software or view, copy or compile the Source Code of the Software.

pigfuckers, putting that shit on GitHub with a "don't look at it" license

I don't actually understand what this VS Code extension provides?

  > Behind the scenes, this extension is using a Docker-based local proxy (via Neon Local) to route traffic from localhost to your Neon database branch. The extension handles authentication, networking, and branch selection for you. All you have to do is select which branch you want to connect to and run your application.

  > The extension launches a local Docker container that exposes a static Postgres connection at localhost:5432. Your app connects using a fixed connection string: postgres://neon:npg@localhost:5432

And then you're meant to read this connection string from an ENV var

This seems like an obscenely complex way to essentially set an ENV var pointing at a given database.

I can either install a VS Code extension, and enter my Neon info in it's UI to set this ENV var, or...

I can change the PG_URL in my .env file to the same info I would have entered in the extension UI, right?

Am I missing something?