I tried vscode the other day to see what it's about and it's nice, but I found plugin development convoluted and very limiting compared to emacs. No chance of quickly writing a script to automate something in the editor, because it takes so much time that it's not worth it for quick editor code snippets. Other editor users simply have no concept of how easy it is to whip up some quick script to perform some task in e…
> No chance of quickly writing a script to automate something in the editor, because it takes so much time that it's not worth it for quick editor code snippets. Take a look at Atom[0]: you can almost think it's a bit underpowered Emacs that uses CoffeeScript(JS) instead of Elisp. It uses the same mental model as Emacs; the init file is a CoffeeScript file, not a JSON file with packages (like VSCode). [0] atom.io
Emacs 26.3
81–90 of 165 posts
Re: Emacs 26.3
#82Earlier quoted context omitted.
Emacs performance in general (not just Windows) has been a complaint forever. Back when Emacs was first launched, and machine memory was measured in megabytes, people joked it stood for Eight Megabytes And Constantly Swapping.
Only back then it was true. Now it’s only slow on Windows for some reason (and maybe not universally so, though I don’t use Windows enough to have bothered investigating).
Re: Emacs 26.3
#83Earlier quoted context omitted.
Personally for me spacemacs is bit slower in startup for my liking, so I use my own custom configuration. It's just lisp at the end of the day. Also for people who prefer emacs keys instead of vi, they can start with emacs-prelude package. But it will be hard to beat custom configuration in long run.
> Personally for me spacemacs is bit slower in startup for my liking I have see this many times and never understood how startup time could be an issue. I startup Spacemacs at the beginning of the day, and close it when I leave. 10 second of startup time is nothing.
Then again it may be the case that part of the cycle is seeing if the package management system of your custom distro (be it spacemacs, doom, or whatever) picks up and configures the new packages correctly.
Re: Emacs 26.3
#84Great job a very good example of programmable editor. Emacs had been my work horse since 2002 and never disappointed. In the meantime tried many ide only vim and emacs stayed with me. Sometimes do use nano and sublime text but then back to either emacs or vi. All those shiny IDE based on electron, Java or C++ are just too slow to be productive be it VScode, atom or eclipse or visual studio or kdevelop. I am forced to…
Re: Emacs 26.3
#85The improved js-mode in 27.x is definitely worth checking out, especially if you use React/JSX. Had many issues wrestling with indentation in previous setup. https://github.com/mooz/js2-mode/blob/master/README.md#react...
Consider the poor quality of the existing js modes for 26.x, any idea why this depends on a future version of Emacs instead of current versions? Alternatively, could somebody convince the author of the railwaycat port (Emacs with better macOS integration) to get a version 27 out soon?
You might as well look at the thread js2-mode was revoked[0] and ergoemacs' article[1].
> Alternatively, could somebody convince the author of the railwaycat port (Emacs with better macOS integration) to get a version 27 out soon?
Er... I would like to point out that it's not 'railwaycat' port but more of Mitsuharu Yamamoto's port[2], and AFAIK he has claimed that he has no interest in maintaing an emacs27 version.
[0] https://lists.gnu.org/archive/html/emacs-devel/2009-08/msg00... [1] http://ergoemacs.org/misc/emacs_javascript_mode_war.html [2] https://bitbucket.org/mituharu/emacs-mac
Re: Emacs 26.3
#86Great job a very good example of programmable editor. Emacs had been my work horse since 2002 and never disappointed. In the meantime tried many ide only vim and emacs stayed with me. Sometimes do use nano and sublime text but then back to either emacs or vi. All those shiny IDE based on electron, Java or C++ are just too slow to be productive be it VScode, atom or eclipse or visual studio or kdevelop. I am forced to…
The one thing that keeps me from moving lightweight editors like vim or emacs from the bloated IDE stuff if the ability to easily find definitions, etc. If I have hundreds or thousands of source files and I want to find the definition of say a struct or function, being able to right click->go to definition or similar is a godsend. Maybe emacs or vim have similar features via plugins though? I'm not sure.
What they usually can't do is the more involved stuff, like refactoring, because there is no company who pays people to implement these for emacs/vim.
Re: Emacs 26.3
#87The improved js-mode in 27.x is definitely worth checking out, especially if you use React/JSX. Had many issues wrestling with indentation in previous setup. https://github.com/mooz/js2-mode/blob/master/README.md#react...
Consider the poor quality of the existing js modes for 26.x, any idea why this depends on a future version of Emacs instead of current versions? Alternatively, could somebody convince the author of the railwaycat port (Emacs with better macOS integration) to get a version 27 out soon?
Re: Emacs 26.3
#88Earlier quoted context omitted.
> No chance of quickly writing a script to automate something in the editor, because it takes so much time that it's not worth it for quick editor code snippets. Take a look at Atom[0]: you can almost think it's a bit underpowered Emacs that uses CoffeeScript(JS) instead of Elisp. It uses the same mental model as Emacs; the init file is a CoffeeScript file, not a JSON file with packages (like VSCode). [0] atom.io
Does it also offer an api for plugins, instead giving access to all of the editor like emacs? Because that is one thing I found limiting in vscode that I can do only what the api devs thought of.
I'm not sure what you're asking; Emacs also exposes a set of APIs. If you're asking if Atom's init file is written as a generic programming language (unlike VSCode which uses JSON), yes it is.
If you're asking if Atom's API is sufficient enough to implement radical modes (like js2-mode in Emacs), AFAIK yes. Atom by default doesn't have a terminal or a browser; but there are several packages to do them. However I'm not too familiar with the Atom's API surface; I've never used Atom as a primary editor, but more of a backup editor for when I'm recompiling Emacs/reinstalling Emacs packages, ... so I'm not sure about the last sentence.
Re: Emacs 26.3
#89Earlier quoted context omitted.
Of all the problems Guile Emacs might have fixed, performance on Windows is not one I considered.
I don't know if it would, but I can imagine that replacing the aging Elisp interpreter would improve the situation on all systems.
Re: Emacs 26.3
#90The improved js-mode in 27.x is definitely worth checking out, especially if you use React/JSX. Had many issues wrestling with indentation in previous setup. https://github.com/mooz/js2-mode/blob/master/README.md#react...
That is very good to hear. I've used Emacs for a decade, but I recently switched to VS Code because JSX support in Emacs was such a mess.