Communities that rally around a product are an essential part of choosing a Tool for Thought. Tools for Thought are such significant investments on the part of users to master them that having a community to support them is crucial.
6/10 Since they are open-source, you can follow and participate in their development process. You can submit ideas, bug reports and even contribute to the code base.
I am two weeks into my deep dive. There are many things I like and a few that I hope will improve. Let me give you an update.
Bottom line: If you prefer Outliners and want local first, Logseq is a solid choice.
2/13 Every day I learn something new while using Logseq & I feel I have barely brushed the surface.
The outliner is an excellently implemented standard "Outlining" tool (folding, zooming, expanding/collapsing).
Any outliner veteran will feel at home in Logseq.
3/13 Interaction - mouse/keyboard
In addition to solid mouse support (drag, drop, create block refs), it has excellent keyboard support. It seems anything you can do with the mouse can be done with the keyboard.
1/6 @logseq deep dive continues... today some words on performance.
Some time back, I did a performance test on Logseq, but it didn't pass my expectations. Many graph DB-based Tools for Thought didn't do so well in the past. #TfT
However, things have changed for the positive.
2/6 I know engineers always intend to make speed a priority, but the truth is, early in the development process of a new TfT, it's easy to skip that part and focus on rapid iterations of features.
It is a tough balance to strike: new features that users demand and speed.
3/6 Most users don't notice this since they start with a small collection of notes & slowly add. But, as the months pass into a year or so, performance becomes a big issue.
When users notice it, they really notice it & rebel. Performance is a big reason people will switch tools.
I am on day 3 of my deep dive into Logseq. Also, I am using Tana in parallel, inputting the same data, tags, and structure into each tool. (Is anyone curious about my observations? 😏)
However, today's thread is about Logseq's template feature. #TfT
2/ This is another important feature, and Logseq has us covered.
It is super easy to define a template with bullets, structure and metadata (properties).
As shown here, right mouse click on a node and define it as a template.
To use the template, type /Template
3/ The template feature allows for inserting dynamic variables for dates and current page. Perhaps there are more variables? I don't know. Here is what is documented:
1/ I have been doing a test phase with @culturedcode's Things 3.
I admit it's a crazy thing to do, but I had to put this app through the "#TfT Hacker" productivity test.
So this probably has no value to my reader base, but I feel compelled to talk about this app.
2/ Things is a task manager known for its beauty and simplicity.
The Things UI is done right.
For some reason, when I see my daily task list in Things, I don't feel overwhelmed due to its focus on what is relevant right now and its generous use of luscious white space.
3/ They say Beauty is only skin deep. But don't be fooled, while Things is praised for its beauty, it's not just another "pretty" app.
It embodies a true and tested system for dealing with your tasks and projects.
Today I forced myself to take meeting and planning notes all day in Logseq. I am an old-time Outline lover. And I have to say it feels very natural. #TfT
I will continue the rest of the week doing so.
2/ Outlining is smooth. The keyboard is responsive and works the way an outline should regarding indenting, outdenting, zooming, page navigation, and rearranging nodes between levels and hierarchy.
If you like outlining, you will feel at home.
3/ I created a bunch of namespaces for organizing primary nodes I often use in note-taking into logical structures. Namespaces never really did anything in Roam, so I was "educated" today on their value in a tool that supports them.