Case in point: #logseq my beloved note-taking outliner shot itself in the foot by splitting its codebase and for all intents and purposes dropping its Markdown file-based backend for a SQLite database. Its development was already stagnant and this amounted effectively to a coup de grâce if you ask me.
#logseq is written in the beautiful programming language #clojure one so niche that contributing to the project must be like joining a software engineering circlejerk just for software engineering’s sake. UI, UX, roadmap, performance, et al. be damned.
And still #logseq concepts were sound, many users myself included validated it with our own data.
That’s why I for one welcome #tine a lightning-fast, multi-platform, compatible #loseq re-implementation written in butt-ugly #rust with the help of #claude #AI
And maybe, just maybe, this is how #foss projects get killed and reborn by #AI
https://github.com/martinkoutecky/tine
#android #obtainium
Related:
If you're not super happy with #Logseq's project direction (they spent countless months working on a new database-based version of the program, abandoning the original Markdown-files-based approach), I bring you some good news and bad news.
The good news is that https://tine.page is a new open source alternative that looks decent, can simply pick up your markdown files from Logseq, and adds some new features.
The bad news is that it's vibe-coded.
I guess this is becoming a familiar dilemma these days. And I still haven't quite figured out how vibe-coded software can be open source, or under any sort of copyright, for that matter.
Previously:
quotingAt last. #logseq is back.
nevent1q…q743
https://github.com/logseq/logseq/releases/tag/2.0.1