@lyse@lyse.isobeef.org flawed is the right word, no harsh at all. Good reading, and thanks for supporting the possibility of convincing @prologic@twtxt.net to switch to a database! :-D :-P

Not gonna happen 😆 But thanks for trying 🤗

@prologic@twtxt.net boo, boo, boooooo! :-D :-P

I really don’t understand why I’m getting such a hard time from y’all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔

@prologic@twtxt.net not me mate, I asked as I was genuinely curious and as someone who only really knows SQL as far as databases go, I keep wondering what life is like on the NoSQL side of the fence 😅

@abucci@anthony.buc.ci Where did I hate on SQL databases? 🤔

Anyway, even if I did, which I’m sure I did, it wasn’t intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn’t really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it could. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦‍♂️

As a big proponent of self-hosting, I find this an anti-pattern.

@abucci@anthony.buc.ci Hmm this is true, sadly. Are you able to file a feature request for this? It’s just a missing feature 🙏