I’ve never liked the idea of having everything displayed all of the time for all of history.

And I still don’t: Search and Bookmarks are better tools for this IMO.

From a technical perspective however, we will not introduce any CGO dependencies into yarnd – It makes portability harder.

Also I hate SQL 😆

@eldersnake@we.loveprivacy.club Several reasons:

• It’s another language to learn (SQL)
  
• It adds another dependency to your system
  
• It’s another failure mode (database blows up, scheme changes, indexs, etc)
  
• It increases security problems (now you have to worry about being SQL-safe)
  

And most of all, in my experience, it doesn’t actually solve any problems that a good key/value store can solve with good indexes and good data structures. I’m just no longer a fan, I used to use MySQL, SQLite, etc back in the day, these days, nope I wouldn’t even go anywhere near a database (for my own projects) if I can help it – It’s just another thing that can fail, another operational overhead.

@eldersnake@we.loveprivacy.club Sorry, @lyse@lyse.isobeef.org just pointed out to me on IRC at some ungodly hour this morning (woke up for some reason) that all my arguments are flawed 🤣 Regardless of my experiences and reasoning, I prefer to use bitcask for most things “dadtabase”(ish) and the “right data structures” for things I’m working with, be-it a key/value store, in-memory hashmap, write-ahead-log(s), indexes, etc. Perhaps I find it more comfortable and easier to use lower-level libraires to solve the same kinds of “data” needs.