4 ms·
In reality, it is very easy in vscode. The difference is, that in vscode it is a easily readable json. Much, much! better than in both emacs and vim. Edit: dow
by 101404 6y ago
In reality, it is very easy in vscode. The difference is, that in vscode it is a easily readable json. Much, much! better than in both emacs and vim.
Edit: downvoting doesn't change reality
- diffeomorphism 6y agoSo which is it: VS Code is maximally unsuited for everyone or the previous argument was nonsense?
- 101404 6y agoYour comment doesn't make sense. What are you trying to say?
- diffeomorphism 6y agoELI5: - Article: Non-trivial config is bad. Hence emacs is bad but VS is good. - My post: Not having non-trivial config is bad. - Your post: VS has non-trivial config and even more/better than emacs. - My reply: So do you agree with article and now VS is "maximally unsuitable for everyone" (the quote for "bad" from the article)? Or do you disagree with article?
- 101404 6y agoYou didn't read the comments correctly, hence your confused reply.
- mtts 6y agoIn Emacs it’s easily readable ELisp. Much, much better than JSON. Well, more versatile, anyway.
- u801e 6y agoIn vim, configuration is either through running commands you could run in normal mode in vim, or through vimscript functions. I assume emacs is similar in that regard. JSON isn't really that easy to read unless it's pretty formatted, and it's somewhat difficult to write (making sure you have every double-quote, every comma, every closing and opening bracket/brace, etc. I always have to run a JSON linter to make sure I didn't miss anything when writing JSON by hand.