Where is the "networked mode" in Turso? Turso's readme and docs do not mention anything like this
[flagged]
Deep dive into Turso, the “SQLite rewrite in Rust”
11–20 of 154 posts
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#12Where is the "networked mode" in Turso? Turso's readme and docs do not mention anything like this
[deleted]
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#13> ... most of which can be fixed by a rewrite in Rust
huh? That is clearly not the case. memory bugs - sure. Not having a public test suite, not accepting public contributions, weakly typed columns and lack of concurrency has nothing to do with the language. They're governance decisions, that's it.
>I see this situation trhough the prism of the innovator's dilemma: the incumbent is not willing to sacrifice a part of its market to evolve, so we need a new player to come and innovate.
I don't think the innovators dilemma quite applies in the open source world. Projects are tools, that's it. Preserving a project for the sake of preserving it isn't a good idea.
If people need to run a sqlite db in these exotic places, shedding it means someone else has to build their own tool now that can do it. Sqlite has decided that they care about that, so they support it, so they can't use rust. Seems sound.
Projects coming and going is a good thing in open source, not a bug.
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#14> ... most of which can be fixed by a rewrite in Rust huh? That is clearly not the case. memory bugs - sure. Not having a public test suite, not accepting public contributions, weakly typed columns and lack of concurrency has nothing to do with the language. They're governance decisions, that's it. >I see this situation trhough the prism of the innovator's dilemma: the incumbent is not willing to sacrifice a part of…
Maybe they're saying a rewrite part solves the governance issues not the rust part.
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#15Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#16I hate to be negative, but where is the deep dive? This is a shallow overview of Turso's features and some of the motivation behind it. Am I missing something?
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#17> ... most of which can be fixed by a rewrite in Rust huh? That is clearly not the case. memory bugs - sure. Not having a public test suite, not accepting public contributions, weakly typed columns and lack of concurrency has nothing to do with the language. They're governance decisions, that's it. >I see this situation trhough the prism of the innovator's dilemma: the incumbent is not willing to sacrifice a part of…
I know I've seen multiple bug reports in open source projects with "well we can't fix this because it'd break things for existing users." Maybe it's a bad thing, but why do you think this doesn't happen?
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#18I’d imagine this will go a bit like the rust rewrite of sudo etc. Despite the memory safety advantages at least towards the start it still ends up more fragile because the incumbent has years of testing and fixing behind it
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#19At the current rate of progress I'm wondering how long it will take for llm agents to be able to rewrite/translate complete projects into another language. SQLite may not be the best candidate, due to the hidden test suite. But CPython or Clang or binutils or...
The RIIR-benchmark: rewrite CPython in Rust, pass the complete test suite, no performance regressions, $100 budget. How far away are we there, a couple months? A few years? Or is it a completely ill-posed problem, due to the test suite being tied to the implementation language?
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#20[deleted]