3 ms·
What news did you see that was disheartening? The only story I was was that helm is being put to pasture, but that's very separate from Emacs itself. I think E
by kstrauser 6y ago
What news did you see that was disheartening? The only story I was was that helm is being put to pasture, but that's very separate from Emacs itself.
I think Emacs has missed some of the excitement of, say, VSCode because until recently it hasn't had many opinionated guides to using it (like Spacemacs or Doom Emacs). I've overheard a lot of conversations like:
New user: OK, got it installed! Now what should I do?
Emacser: Anything you want!
New user: I want to write Python. What's a good way to do that?
Emacser: Here's 47 similarly named but substantially different Python modes. Choose the one you like!
New user: Which one do you like?
Emacser: I started with one I found in a GitHub gist, then modified it to do remote editing over a 3270 terminal. You should check it out!
New user: ...
There's a lot to be said for the VSCode approach of "here's the golden path to doing ${thing}. Once you've learned it, you might try the alternatives to see if some are a better fit for you." Alternatively, consider the analogy of a Linux distro that gives you a well configured KDE or Gnome environment, but that lets you switch to another DE once you've been using it for a while. Now Spacemacs and Doom Emacs are providing that experience to new users, and I've heard more excitement about Emacs in the last couple of years than in the previous decade.
- rashkov 6y agoThis is why I recommend spacemacs: just install the python layer, read its readme file, and get going. Emacs is like clay, but that’s only useful once you’re comfortable with it. Until then better to get an opinionated experience out of the box, and tweak it from there.
- loosetypes 6y agoI love emacs but lately I’ve been feeling this approach is very much at odds with today’s expectation of per-project convention-flexibility within a dialect, a la prettier.
- kstrauser 6y agoTruthfully, I feel kind of the same way. There are parts of my .emacs.d/init.el that go back 25 years, so I'm not saying this from the position of "I tried it last week and it wasn't like my other editors so I don't like it." One of the things I love about VSCode, and that made me seriously evaluate it in the first place, is how easy it is to configure per-project settings like "use this virtualenv when editing these files". In VSCode, that looks like having one window per project and this works great. When I'm in the middle of working on one thing, I can quickly open a second window, hack on something, close that window, and get back to what I was doing. Since Emacs has one flat memory space, that's not nearly so easy. I love Emacs and would go back to using it in a heartbeat if it were half so easy to set up and maintain a working Python development environment with all the bells and whistles, but so far I haven't found that to be the case.
- theCodeStig 6y agoDirenv and lsp-mode