I'd really like to see what the value proposition is over org-mode first and foremost. Yes it runs on Neovim (is it exclusive to Neovim?), but vim-orgmode is a

I'd really like to see what the value proposition is over org-mode first and foremost. Yes it runs on Neovim (is it exclusive to Neovim?), but vim-orgmode is a thing. From watching the videos, the guy mentions that a problem early on was that it was constantly compared to org-mode, which was confusing to people not familiar with org-mode, so I guess they're trying to get away from that? I watched a few videos and saw syntax and features almost identical to the most basic level of org-mode. The one feature it seems to have over org is that it uses a C++ based parser, which might be faster than the mostly elisp parser from org-mode? But even that means it relies on features of C++14, which isn't included with macOS, so I'm left feeling like this is half anti-feature compared to org-mode's highly portable parser: If Emacs works, org-mode will work, and Emacs is mostly elisp itself, so if the elisp interpreter works, Emacs will work. If I can run an executable I can run org-mode essentially, but this requires I'm allowed to install a whole new compiler on a machine before using it. I think it was Prot that put forward a strong case for building an org-mode specification with multiple compatibility levels, so that tools for other platforms could say they implement a certain subset of its features and syntax using a simple shorthand like "Org-Mode Level 3 Compatible". I'd like to see that effort go further.