Can anybody comment on Logseq's performance compared to Obsidian?
Obsidian is perfect for my needs but unfortunately a tad too heavy for my poor laptop with 4 GB RAM.
Obsidian is perfect for my needs but unfortunately a tad too heavy for my poor laptop with 4 GB RAM.
That said, I actually _use_ Logseq due to the way it works (i.e., an outliner). Obsidian simply doesn't meet my needs.
I have a few questions for you. I apologize if some (all?) of them are too aggressive.
What were your reasons for creating a new project rather than focussing on the existing project? Technical debt?
What will be the pricing of the new app? Will it be open-source?
Lastly, will Notes be maintained by you to a lesser degree upon the release of Plume? Will you let the community take over? Will nothing change?
1. Notes is completely open-source[1]. There are some awesome maintainers who help me fix and update things and sometimes even implement new features. When Plume will be released, of course, I'll put much less time into Notes (as already the case). But since Notes is licensed under MPL and Plume is built on top of it, all files used from Notes will be open source as well, so any improvement from Plume could be potentially incorporated into Notes.
2. The reason for creating Plume is that I always wanted[2] to create an advanced editor (a la Notion) but only recently realized how to be able to do it using C++ (handling the model) and QML (handling the view). I had to implement many things from scratch (undo/redo/copy/paste/multi-block-editing/etc).
3. I recently discussed my reasoning to go close-source[3]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.
[1] https://github.com/nuttyartist/notes
For getting used to the motions especially https://vim-adventures.com can be a fun way, in its game format.
For getting started I’d say don’t worry about plugins much, but get https://github.com/tpope/vim-sensible at least so the defaults meant for vi don’t get in the way. The only other thing you might want is a format syntax if your preferred note syntax isn’t highlighted well by default or something. Polyglot can be good to stave that off but really I’d say learn on a really lean config, and get used to using :help or similar. It’s the best way to learn the parts that work everywhere.
Honestly I’d do the vimtutor, maybe try the free version of this, and just use it for a bit. Use the arrow keys, use the mouse (:set mouse=a turns it on just in case) but see how you like being able to use the <count><action><range> syntax to do things. That’s the real win in my opinion, things like reflow this paragraph gqip (reflow is gq, range for a paragraph is “ip” or In Paragraph), delete this sentence including surrounding spaces and period das (literally Delete Around Sentence), and with movements gU} changes the rest of the current paragraph to uppercase.
There are many lists of these things, but I learned it by treating it as notepad with some odd bindings for save and quit for a bit in college then whenever something was annoying looking up how to do it or how to build it. I’ve now been using vim as my main editor for notes, prose with latex or markdown, and programming for 20 years, and literally given courses on it for graduate students. That is to say, you don’t need to learn it all ip front to use it. Learn how to open it, get in insert mode, write and quit and jump in; hopefully it will fit you like it did for me.
It is a modal editor just like vi/vim/neovim, but way better/easier/sensible/helpful than its much older ancestors, especially for new learners. Even if you will later on decide to switch to something like neovim, this switch is going to be a relative piece of cake, after you had experience and understood the basic idea behind modal editing, compared to trying to go vim cold turkey.
According to my experience the vast majority of "vim beginners" actually already have a significant amount of experience with vim; it's just that the experience was negative, they didn't get far and were overwhelmed, unfoundly blaiming themselves and their own stupidity, hoping that all they are missing is a good tutorial. No, it's not you. It's the editor itself, build in 70s with the ideas, UI, hotkeys that are inapropriate for the current time. There is a much better way for modern times.
Install Helix, run it and type ':tutor' to access the tutorial. After that you will be ready to go.
This is the case for me too. I tried vimtutor, paid for many high quality courses directed at beginners but it never really clicked for me.
Thanks for the comment!
Org-mode can be used simply, but the kind of person drawn to org-mode (e.g. me) has a hard time not yak shaving org-mode in the extreme. :-)