"This guide is meant as a loose inspiration for a poweruser looking to switch to Linux."
It's your guide, but as a non-technical Linux power user of over 2 decades, I don't think I would recommend Windows or Mac power users make the immediate shift to the (Neo)vim and i3 "metaphors" (if that's the right way to express it). I'd recommend KDE for Windows PUs and Pop? Peppermint? (I forget which disto aspires to the MacOS look and feel.
I started using Emacs for Org because I don't program, and I gradually added email, file management, irc, gopher, roam, and other "functionality" as I became more proficient. I finally switched any key binding I could anywhere to Emacs, but I would never suggest Emacs to a Windows or Mac PU unless they already used it, let alone modal editing if they never used it and didn't live in a text editor.
When I started using Org there were not many decent open source plaintext information managers that could also do agendas, to-dos, etc. I mostly used Zim prior. Not all PUs live in text editors, program, or edit configuration files in a modal editor. Why would someone who uses a text editor primarily to edit configuration files do so in a modal editor unsteady of Gedit or Kate or even nano or micro?
Today, I would likely recommend Joplin for a PU who wants open source plain text information management plus a multitude of plugins on any platform and any GUI text editor with good syntax highlighting and customization and a Desktop Manager. It would allow for more gradual transition because being a PU on Windows or Mac means making significant changes would actually be more difficult.
But you can have my Emacs when you pry it from my cold, dead hands.
It's your guide, but as a non-technical Linux power user of over 2 decades, I don't think I would recommend Windows or Mac power users make the immediate shift to the (Neo)vim and i3 "metaphors" (if that's the right way to express it). I'd recommend KDE for Windows PUs and Pop? Peppermint? (I forget which disto aspires to the MacOS look and feel.
I started using Emacs for Org because I don't program, and I gradually added email, file management, irc, gopher, roam, and other "functionality" as I became more proficient. I finally switched any key binding I could anywhere to Emacs, but I would never suggest Emacs to a Windows or Mac PU unless they already used it, let alone modal editing if they never used it and didn't live in a text editor.
When I started using Org there were not many decent open source plaintext information managers that could also do agendas, to-dos, etc. I mostly used Zim prior. Not all PUs live in text editors, program, or edit configuration files in a modal editor. Why would someone who uses a text editor primarily to edit configuration files do so in a modal editor unsteady of Gedit or Kate or even nano or micro?
Today, I would likely recommend Joplin for a PU who wants open source plain text information management plus a multitude of plugins on any platform and any GUI text editor with good syntax highlighting and customization and a Desktop Manager. It would allow for more gradual transition because being a PU on Windows or Mac means making significant changes would actually be more difficult.
But you can have my Emacs when you pry it from my cold, dead hands.