←back to thread

212 points todsacerdoti | 4 comments | | HN request time: 0s | source
Show context
bfrog ◴[] No.43109740[source]
This is a really cool set of articles, and while it’s not going to replace sqlite it’s fantastic to see the pieces needed to do sql with SQLite’s file format
replies(1): >>43109976 #
rockwotj ◴[] No.43109976[source]
SQLites alternative in rust is a thing though

https://github.com/tursodatabase/limbo

replies(3): >>43110098 #>>43110247 #>>43113755 #
usrbinbash ◴[] No.43113755[source]
"alternative" implies that this is either on a comparable level of battle-testedness and feature completeness as sqlite, or that it solves problems that sqlite has, or that is delivers substantiable, or at least noticeable advantages over sqlite.

So, which of these points apply?

replies(1): >>43115907 #
1. sejje ◴[] No.43115907[source]
I don't think it implies any of that.

I think it means you might use it in similar situations. Like when you want an in-memory database.

replies(1): >>43117934 #
2. usrbinbash ◴[] No.43117934[source]
No I might not. In these similar situations, I will use sqlite, unless someone can point out one of the items listed above as a reason to use something else.
replies(1): >>43120386 #
3. NoahKAndrews ◴[] No.43120386[source]
Just because you don't like it doesn't make it not an alternative. Even if it's objectively worse, it's still an alternative.
replies(1): >>43125614 #
4. usrbinbash ◴[] No.43125614{3}[source]
> Just because you don't like it

Read my post again. Sympathy or lack thereof don't factor into this equation. This is about battle-testedness and features. I don't make technical decisions based on emotions.