Hacker News Reader

Comment by diffeomorphism | Hacker News Reader

> The fact that everyone has to have a non-empty, non trivial .emacs file means it is maximally unsuitable - for everyone.

The fact that you don't have one for VS Code shows that any modifications to make it better are too difficult and that you just have to make do with how it comes out of the box.

View on HN

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

In 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.

In Emacs it’s easily readable ELisp. Much, much better than JSON.

Well, more versatile, anyway.

So which is it: VS Code is maximally unsuited for everyone or the previous argument was nonsense?

Your comment doesn't make sense. What are you trying to say?

ELI5:

- 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?

You didn't read the comments correctly, hence your confused reply.

I use VS Code sparsely but this is what has worked for me https://marketplace.visualstudio.com/items?itemName=Shan.cod...

Reply on news.ycombinator.com