Another HN thread about Emacs. I don't think I've ever seen anyone using Emacs as a daily driver editor in the past 5 years...

@nuclear why people talking about Emacs is a problem for you ?

If they want to talk about, it's totally Ok.

I daily use Emacs since more than 10 years, for a lot of things (not only code). I'm verry happy with that. But regularly, I meet people who think its unacceptable for someone to use Emacs. And they generally act in a bad way.

@postroutine It's not a problem, it's just that there are superior alternatives and it's obsolete.

@nuclear "superior ajternatives", "obsolete": Two very wrong ideas.

@postroutine Superior as in able to complete the same tasks faster and easier while requiring no time to be spent on configuration, or able to complete tasks impossible for the counterpart.

@nuclear Emacs is fast and simple. Seeing the configuration and the learning of a tool as a bad thing is arbitrary. And I can do with Emacs every things I want or need.

The problem is that you see what you prefer as an universal requierment. Peoples have differents needs and that why there is no superior tools. The goal is to offer to people what they need or want. For some it's Emacs, for other it's something else.


@postroutine What you're talking about is hard to understand, because it's abstract. Here's something concrete:

After more than half an hour of tinkering with a huge config (most of which was already written beforehand), Emacs is nowhere near what VS Code offers out of the box. And even the best config you can think of sucks in terms of e.g. Intellisense, UX, UI freezing because there is only 1 thread, random packages breaking, etc.

· · Web · 1 · 0 · 0

@nuclear I don't speak in abstract, but in general. And your video is not concrete:
It's one use case for you on which you don't know how to use Emacs in it.
That doesn't mean Emacs can't do it.

@nuclear Again, thinking that learning and configuring a tool as a bad thing is subjective. You think is bad doesn't mean it is for everyone.

The time spend in learning and config a tool, like a text editor, is insignificant to the time spend to use it.
And regardless to the tool, learning how to use it will allow you to get the most out of it.
It's not a bad thing to learn and customize your tools.

The "out of the box" is not an argument. It's your preference.


@nuclear User experience with Emacs is very good. It's different, but but there is not only one user experience.
UX need to take must take into account the context, the profile and experience of the users.
And you don't design a text editor like a music player: You don't interact the same among of time with the two software.

@nuclear About the UI freeze: Never had it while I was coding.
Emacs is designed to delegate heavy works to external tools, who run in async.
Emacs done the text display and manipulation, but code analysis, the error check, are done by external tools started by Emacs.
Emacs communicate with the launched tool and provide the UI to interact with what the external tool have done.

And Emacs can interact with a lot of tools who provide informations and manipulations of the code and its structure.
You can even use Language Servers.

@nuclear After more the 10 years, I never have a random package breaking.
In general, Emacs have been more stable for me than any IDE or text editor which was imposed on me at school and work.
And I used Emacs for more time than the others tools.

@postroutine Give me the best Emacs config for React + Typescript you can come up with, and I will explain why it's objectively inferior to a stock VS Code. I've been using Emacs for years and know very well how to configure it and what plugins there are. It's not worth it.


"Give me…"

I owe you nothing.

"…inferior to…"
"It's not worth it."

Again. OK, I block you.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!