You have ten seconds to explain why you aren't using Spacemacs.

It's lincucks.

>>59847217
Because Emacs is a terrible editor.
Yes I tried it.

>>59847217
not based on superior electron

>>59847217
I use space vim. It's pretty.

>>59847217
janky as fuck

>>59847217
Never heard of it, I already switched to neovim.
Can I go on now? I need to do stuff.

>>59847217
I'm using regular Emacs. Why should I be using Spacemacs? I'm pretty new to Emacs so you still could convince me to change my ways. Also considering Evil mode

>>59847941
I tried evil mode. It will drive you insane because every second buffer will turn it off. Wasted a week trying to configure it and eventually gave up. Would recommend just using vim/neovim

>>59847217
I can't activate it with CIA nigger's license.

>>59847217
I'm using it. Pretty cool.

>>59847941
Layers and vim controls.

>>59847217
I don't want to learn lisp.

>>59847217
nano. enough said.

>>59847217
vanilla emacs is already too slow and clunky for my taste.

I'm not an octopus so I use vim

One thing I dislike about emacs is that it can't display graphics in a terminal emulator.

w3m can do that, but emacs requires creating a whole new window that doesn't obey my terminal settings.

The Right Size of Software

There is a hidden dual of the Unix gospel of small, sharp tools; a background so implicit that many Unix practitioners do not notice it, any more than fish notice the water they swim in. It is the presence of frameworks.

Small, sharp tools in the Unix style have trouble sharing data, unless they live inside a framework that makes communication among them easy. Emacs is such a framework, and unified management of shared context is what the optional complexity of Emacs is buying. The practical impact of unified management of shared context is that the user is not burdened with low-level naming and resource-management issues.

In old-school Unix, the only framework was pipelines, redirection, and the shell; the integration was done with scripts, and the shared context was (essentially) the file system itself. But that was not the end of evolution.

Emacs unifies the file system with a world of text buffers and helper processes, largely leaving the shell framework behind. Wily is also about buffers and helpers, but incorporates the shell framework into itself. Modern desktop environments provide a communication framework for GUIs, also leaving the shell framework behind. Each framework has strengths and weaknesses of its own. Frameworks become homes to ecologies of tools — the shell to shellscripts, Emacs to Lisp modes, and desktop environments to flocks of GUIs communicating both via drag and drop and by more esoteric means such as object brokers.

>>59847217
I just use eclipse