glommer

7 ms·

31.
by glommer 2y ago
thanks. I am sad, but not that surprised, that a lot of people here are interpreting this as we claiming that we're already faster than sqlite all over. I don't even care about being faster than sqlite, just not being slower, this
32.
by glommer 2y ago
then we'd have to ship with a PHP driver from day1.
33.
by glommer 2y ago
dunno, we rewrote a database before, much larger and harder than sqlite, and it was pretty successful. In my experience the 10% that doesn't get done is the 10% that people don't care too much about it anyway.
34.
by glommer 2y ago
author here: fully compatible at the language and file format level. Further down the post I actually call out explicitly that we do intend to get rid of some of the baggage.
35.
by glommer 2y ago
damn =(
36.
by glommer 2y ago
be careful with that, though. In a lot of ways it is still slower. The goal with that was just to demonstrate that there's nothing really there that is fundamentally slower, and the perf is already on par in the areas where we spent cy
37.
by glommer 2y ago
absolutely not. We're not fans of public domain, which is one of the things that led us to create libSQL in the first place. It is MIT.
38.
by glommer 2y ago
this is a codename, and if the project is to be successful, we don't expect to keep it.
39.
by glommer 2y ago
Hey Simon! However early you think it is, I can guarantee it is even earlier =) If this is just a standard sqlite database that you are trying to open, though, I'd have expected it to work.
40.
by glommer 2y ago
The goal here is not to claim that it is faster, though (it isn't, in a lot of other things it is slower and if you run cargo bench you will see) It is to highlight that we already reached a good level of performance this early in the
41.
by glommer 2y ago
I was completely unaware of that! How old is that document? I should reach out.
42.
by glommer 2y ago
correct, this is just the project being moved from fun personal side project from the company's CTO to an experimental stage as a company project. There isn't a long term roadmap, or anything like that. I got pretty excited when I
43.
by glommer 3y ago
ok, I can see how the tweet on the top of the article can have that effect. In my defence, this was a humorous tweet that happened in a week where everybody on twitter, frontend and backend, were dunking on each other. So I wrote that in a
44.
by glommer 3y ago
He happened to contribute to our project, but we hired another engineer recently with a lot of great OSS contributions to other project (yrs). Back in our ScyllaDB days, we hired a people from both Linux and LLVM. It's a great way to s
45.
by glommer 3y ago
I can guarantee you're wrong. V is paid top dollar - especially considering his location.
46.
by glommer 3y ago
what was patronizing about my post? Certainly didn't intend to.
47.
by glommer 3y ago
If you go to university for 5 years (which you should), and work your ass off to improve, isn't that "free work" ?
48.
by glommer 3y ago
for posterity, here's the deleted piece: Don’t neglect academic knowledge. One of the unhelpful discussions I see online is the suggestion that you may not need to have academic knowledge to be a “developer”. After all, can’t I just wa
49.
by glommer 3y ago
author here! I had a whole paragraph on the importance of a formal education. But removed because the post was too long. it's very important!
50.
by glommer 3y ago
you can use https://turso.tech for that, which makes SQLite replicated, and available over HTTP. It's designed to work on environments where LiteFS won't (since it needs a volume).
51.
by glommer 4y ago
* extremely easy to get started. * unmatched testability, since you can now run the same code in CI and production and pass .db files to your tests. * extremely cheap and lightweight replication.
52.
by glommer 4y ago
of course it is a library. An embedded database is essentially a library that you add to your application. That you can build stuff around it, doesn't invalidate the fact that the core of it is a library.
53.
by glommer 4y ago
Would love to see your contributions on libSQL!
54.
by glommer 4y ago
I don't want the SQLite trademark.
55.
by glommer 4y ago
rwmj! Now here's a name I don't hear in forever! Hope you're doing great, man! And I won't take offense, I'm pretty rando, though =p
56.
by glommer 4y ago
OP here, and I don't think SQLite is toxic.
57.
by glommer 4y ago
it's not nefarious, it's just a different approach to things. I think Hipp is justified in all he is doing, and I don't think he is necessarily wrong. We just see things differently
58.
by glommer 4y ago
yes, we haven't changed any code yet. There are essentially two approaches here: one of them is to present a finished thing, and the other is to announce your intentions as soon as possible and build every single thing in public. We ch
59.
by glommer 4y ago
What are techniques that I could use to improve my writing ? Always eager to learn.
60.
by glommer 4y ago
That's a really good point. I thought of that myself to be honest but the article was becoming too long and decided to cap. Great point about the link, that's great feedback!

More ›