Live data from Hacker News

Lobste.rs is now running on SQLite

lobste.rs

11–20 of 209 posts

Re: Lobste.rs is now running on SQLite

#16
Some of the cited reasons for moving off MariaDB [1] seem misguided, in my opinion. Especially the part about "K1 are very enterprise-focused, so the database is likely to focus its work on features that are not relevant to us. There's increased risk they drop the free/open source version we use"

K1 acquired the commercial entity behind MariaDB Enterprise, but that's separate from the non-profit MariaDB Foundation. And there's literally zero risk of the MariaDB server suddenly going closed-source; as a fork of MySQL (which is GPL), this is not even legally possible!

[1] https://github.com/lobsters/lobsters/issues/539#issuecomment...

Re: Lobste.rs is now running on SQLite

#17
post #10
post #2

Oh wow. Off-topic but quite refreshing to see a site not absolutely plastered in AI posts

It's a wonderful place. It feels like HN, but with the Silicon Valley attitude dialed way way way down, and with a much narrower scope (politics, economics and entrepreneurship are all off-topic, for example).

Huh. I’ve largely avoided it, but that does sound pretty nice.

Re: Lobste.rs is now running on SQLite

#19
post #11
post #9

No intention to antagonize but... why not postgre? Even my side projects run on postgresql with no overhead at all

Where are you hosting postgres

On the same machine where they are currently storing the sqlite file maybe? It's not that hard to run. A sqlite backup cron is also not that much more work than a pg_dump cron.

Re: Lobste.rs is now running on SQLite

#20
post #9

No intention to antagonize but... why not postgre? Even my side projects run on postgresql with no overhead at all

> run on postgresql with no overhead at all

Citation needed. I love postgres as much as the next person, but it does have more overhead than Sqlite which is in an in-process db linked through compiled C code, it doesn't run as a separate server. Very significant difference that when you use Sqlite db, there is typically no db process other than your application logic, unless you implement the server yourself. If you don't want your application to have multiple processes (say, as a toy example) then it totally makes sense to prefer Sqlite just for this reason. Sqlite and postgres are different tools, they serve different purposes.

Post reply on HN