81–90 of 109 posts
the description as "the next evolution of sqlite" is offensive D. Richard Hipp has done a universal good for the world by releasing sqlite into the public domain and maintaining it for 25 years I bet this VC funded knockoff won't see 5
Pure stolen valor.
Disgusting.
Earlier quoted context omitted.
If it is in-process (as the article says), why do you describe it as client / server architecture? If it’s not in-process why compare it to SQLite instead of other client server databases like Postgres?
There is turso cloud. https://docs.turso.tech/turso-cloud
Earlier quoted context omitted.
I find it crazy that people would ask you in that direction. I would wonder why anyone would chose Turso over SQLite. SQLite is some of the most battle tested software in the world. Turso seems like relatively new software that is still a bit experimental. You do not want your databases to be new or trendy. You want your databases to be solid as a rock.
Sqlite had such a stellar stellar reputation, for so many excellent reasons. I still find it absolutely freakish & abominable that people are so incredibly touchy & reflexively mean & vile to Turso. I've seen a couple Turso centric YouTube's recently and there are dozens and dozens of up votes for what just seems like the most petulant vacuous reflexive bitter viewed comments, dominating the comments. Sqlite deserves…
https://github.com/tursodatabase/turso/pull/4824/files "some performance improvements", no new tests
https://github.com/tursodatabase/turso/pull/4820/ "fix wal checkpoint", one basic test
https://github.com/tursodatabase/turso/pull/4815/ "Optimizer: fix bugs, improve cost model", a lot of nontrivial logic, no new tests
https://github.com/tursodatabase/turso/pull/4814 "WAL auto truncation: increase epoch to prevent stale pages reuse", there's a new test with a comment "It is slightly fragile and can be removed if it will be unclear how to maintain it"
https://github.com/tursodatabase/turso/pull/4806/ "Busy snapshot bugfix" with two new tests with the same comments as 4814 (I guess they didn't fix the bug in one go?)
https://github.com/tursodatabase/turso/pull/4802/ "fix/translate: revert change that allowed index cursor with stale position to be read", fixes a data-corrupting bug, there's a regression test, good (although the original bug sounds like it should've been caught by a suite like the one SQLite has)
That's just a couple days worth of PRs.
This style of development does not inspire confidence. They develop features, sure. But I want my database to be rock-solid and completely covered by tests, not just move fast and break things. It's not FUD to just look at how they approach PRs.
Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en…
Edit: Looking at the go mod file I noticed github.com/mattn/go-sqlite3 which I think is a C wrapper library so I'm assuming you rely on CGO for compiling
Is there an example of a company that rewrote something popular in a faster / better language and built a successful business on that? I can think of ScyllaDB and Redpanda but aren't they struggling for the same reasons: not the default, faster horse, costly to maintain, hard to reach escape velocity
I feel like there's numerous database companies that rewrote an existing database faster/with slightly better features and turned it into a successful product. Just about all of the successful ones really. It's a market where "build a faster horse" has been a successful strategy. Certainly some of the newer succesful database companies are written in more modern languages (for example go with cockroachdb, go original…
Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en…
Which SQLite Go library do you use? My biggest pain with using SQLite in Go is often the libraries and the reliance of CGO which is what puts me off using Turso Edit: Looking at the go mod file I noticed github.com/mattn/go-sqlite3 which I think is a C wrapper library so I'm assuming you rely on CGO for compiling
Commit history is nuts! These guys are working.
It goes to show how future of SE will look like. Loose reviews (a big win for the industry) with each person capable of doing 10x more work, and basically orchestrating/overlooking the work done by the agents. The bottleneck eventually at some point, if not already, will become a fatigue caused by having to process/acknowledge/understand the sheer volume of code spitted out at speeds that we could never have imagined…
Earlier quoted context omitted.
I feel like there's numerous database companies that rewrote an existing database faster/with slightly better features and turned it into a successful product. Just about all of the successful ones really. It's a market where "build a faster horse" has been a successful strategy. Certainly some of the newer succesful database companies are written in more modern languages (for example go with cockroachdb, go original…
I agree you see there's a lot in the database space I just don't know many have reached escape velocity more often they've raised a bunch of venture capital funding and plateau and then have a big problem
Earlier quoted context omitted.
I find it crazy that people would ask you in that direction. I would wonder why anyone would chose Turso over SQLite. SQLite is some of the most battle tested software in the world. Turso seems like relatively new software that is still a bit experimental. You do not want your databases to be new or trendy. You want your databases to be solid as a rock.
Sqlite had such a stellar stellar reputation, for so many excellent reasons. I still find it absolutely freakish & abominable that people are so incredibly touchy & reflexively mean & vile to Turso. I've seen a couple Turso centric YouTube's recently and there are dozens and dozens of up votes for what just seems like the most petulant vacuous reflexive bitter viewed comments, dominating the comments. Sqlite deserves…
In this case, the familiar "rewrite it in Rust" MO has a special angle: the Turso feature list is such a terrifying collection of high-risk, low-performance, inferior, unlikely to be compatible, unproven and unnecessary departures from SQLite that a malicious embrace-and-extend business plan is a reasonable theory and reckless naivety is the best possible case.
Earlier quoted context omitted.
> Amazing test suite. Lol, is that a joke. Seesh. [To be clear, i think sqlite is the hands down winner on this front, no contest. Does the Turso test suite qualify it to be used in safety critical applications? I don't think so]. To your other points - look if it works for you i'm not here to tell you you can't use it. However these features sound more trendy than useful. To me these sound like negatives. A bunch of…
It's just so wild to me that people are so married to anti-features like this. That anti-interest do possesses the modern spirit, enraptures people so. 'i don't know what it is but I'm not interested and it's probably scarey' is not, imo, befitting the cultures I personally want to see. There's times and places for extreme conservatism, but generally I am far more here for progress, for trying for aspiring to better,…
That would be a valid experiment and, if it goes well, a contribution, while hoping that someone bases anything important on Turso looks like grabbing captive users.