5 ms·
> Then a proper editor feels nice. A proper editor for whom? What "proper" means is different to everybody. I already have and use a perfectly proper editor,
by enriquto 5y ago
> Then a proper editor feels nice.
A proper editor for whom? What "proper" means is different to everybody. I already have and use a perfectly proper editor, and don't want to be forced to use another one just to write a few posts somewhere.
> Besides, you can just log in and change something. There’s no need to fire up a terminal,
Alright, but please recognize that this is a subjective point of view. My subjective point of view is the opposite: I'm already on the terminal, and I can just edit some files in there to update a post. There's no need to fire up a web browser, log-in using an ad-hoc login interface, and then use and ad-hoc editor.
- actually_a_dog 5y agoIndeed, emacs and vim are very “proper editors” in this context, which is where having your posts stored as flat files, as is done in most static site blogs, really shines.
- copperx 5y agoYou can also, say, install a plugin to fire emacs to edit a textarea.
- WorldMaker 5y agoPlus these days on Github (and Azure Repos) you can press . and open the entire repo in VS Code (github.dev/vscode.dev) in your browser.
- enriquto 5y agoOr, the other way round, use a terminal-based browser so that you don't need to interrupt your workflow!
- colesantiago 5y agoOf course this point of view is with common developers, so I understand that view. People who are content editors in newspapers, magazines, etc. would highly likely use Wordpress, Ghost or even Substack. In the end, use whatever you're comfortable with, I always go with, "can I extend this" or "will this save me time?" and Wordpress/Ghost almost always gets chosen.
- nicbou 5y ago> please recognize that this is a subjective point of view Yes. This is what we're discussing.