If you do any kind of serious work, you need a text editor. Emacs is still one of the best around. It's fast. It's configurable. And it's under your control. You won't suddenly find your text editor "upgraded" with tons of new features you never asked for. It's all opt-in.

▲

wmedrano 2 hours ago | parent | next [-]

haha, I definitely wouldn't call my setup fast. But it did get a lot better after Native Compilation and a lot of the major stuff has started async to feel more responsive at least.

▲

zhxhhshshs an hour ago | parent | prev | next [-]

It’s slow, bloated and packed to the brim with “features” you will never need.

There is Only One. En garde!

▲

enbugger 2 hours ago | parent | prev | next [-]

> It's fast.

super slow on windows

	▲	asdff 7 minutes ago \| parent [-]
		That's surprising considering it was fast on computers from 30 years ago

▲

hollerith 3 hours ago | parent | prev [-]

>You won't suddenly find your text editor "upgraded" with tons of new features you never asked for.

I never asked for native compilation implemented via the trampoline technique, which increases attack surface (because it causes Emacs to routinely execute files in a known-by-attackers location in my home directory) and makes debugging harder, but I'm stuck with it if I want my Emacs to speak the Wayland protocol (and I do).

Ditto the clumsy bolting-on of lexical scope.

▲

vkazanov 3 hours ago | parent | next [-]

Native compilation is optional as you surely know.

It also has nothing to do with Wayland.

And what's wrong with adding lexical scope!?

I do have some concerns about certain features but the ones listed do work, and work great.

	▲	hollerith 2 hours ago \| parent [-]
		You can't build an Emacs with Wayland (PGTK) support without native comp. ./configure will complain and refuse to do it.

▲

drob518 2 hours ago | parent | prev | next [-]

Sigh. Don’t be “that guy.”

▲

DunningKruger9 3 hours ago | parent | prev [-]

[dead]