3 ms·
> The fewer steps there are between your spinning the IDE and having a working setup What you're overseeing here is that Emacs configurations are usually highl
by tazjin 4y ago
> The fewer steps there are between your spinning the IDE and having a working setup
What you're overseeing here is that Emacs configurations are usually highly individual, and that "a working setup" for _you_ does not mean the same as it does for _me_.
For example, regarding LSPs, I only use them in very rare cases because usually LSP implementations themselves (regardless of the editor you use them in) are buggy and/or slow.
For me it's much more important that the actual _text editing_ experience is consistent across languages, than the tooling for any particular language.
- NeutralForest 4y agoI just disagree with this view, lots of people use it to code. It should be easy to setup a coding environment with it. That's all I mean.
- _a_a_a_ 4y agoLong term emacs user, and I agree. I need to learn to program it but more importantly, I should be able to install a package and have it work because I use emacs for just that - work. There's too much 'add this include your .emacs' etc. But it's getting better.
- pritambaral 4y ago> I just disagree with this view, lots of people use it to code. I agree. It wasn't obvious to me, at first, that Emacs is not a code editor, rather just a Lisp program for editing lots of text. And I didn't even know what Lisp was at the time, so it wouldn't have helped either way. But ... > It should be easy to setup a coding environment with it. It kinda is. I started using Emacs with just a Spacemacs install. And I didn't need to learn anything about Emacs for a long time after that. It was only when Spacemacs stopped being maintained, and I started facing issues due to that, that I looked deeper. It helped that I had learned what Lisp is (Common Lisp, though, not Emacs Lisp) for it to finally click, so I got lucky that way. Now, even when I know Emacs (and Emacs Lisp) rather well, I still stick to Doom Emacs to "setup a coding environment with it".
- celeritascelery 4y agoThe Emacs frameworks (doom, spacemacs, etc) make it pretty easy to setup. That being said, if your primary concern is ease, vscode would be a better choice. Emacs is more focused on power and extensibility.
- NeutralForest 4y agoI know, I'm using Emacs everyday. And I dislike the frameworks because they obfuscate what's going on in Emacs, at least to me. I just think that since we're pushing features like eglot or tree-sitter to core, we should also focus on making them easy to use.
- adalacelove 4y agoI think there will always be some kind of tension. This forces everyone to agree on a particular choice, which may annoy some people but makes it easier to build on top of it. I think that as a matter of fact emacs is highly opinionated, starting with its very extension language, elisp.