That's fine though. Full compatibility doesn't have to mean full backwards compatibility. I think of it as what's Typescript to Javascript.

Once you compile your Typescript to Javascript, Javascript runtimes can run it, Javascript code can call it, etc. Even source maps work.

Once you start using libSQL features, SQLite tools will simply stop working with your databases.

That means the sqlite3 shell stops working, backup solutions like Litestream and sqlite-rsync stop working, SQLite GUIs like SQLiteStudio stop working, forensic and data recovery tools start giving will have a harder time working, etc.

Maybe it's all worth it, but it's not full compatibility, and it should at least be documented.

Well Google's Rust report is already out with great results.. so..

We need to boycott hetzner.

Making their stdlib compatible for other runtimes are huge W! I'd drop some third party libs in favor of them.

I would love to ship my source code (.ts) to npm. But Typescript team was very much against this, as there'll be tsconfig issues and other performance issues. But still fingers crossed.

Then people go crazy when Golang announced they want to enable informed opt-out telemetry.

It's not only that account, other maintainer has been pushing the same promotion all over the place.

Hope it lands soon. DBs are usually locked down with no access to/from internet.

I guess they'll follow NextJS/Vercel or Deno/Deploy book or even License change shouldn't be out of question. Advertise everything as "open source", get free bug reports, contribution, marketing and adoption. Push everything into their commercial offering.