Should I switch to emacs?

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > Should I switch to emacs?

What's the best text editor This poll is closed.
emacs	0	0%
vim	11	20.00%
notepad	2	3.64%
notepad ++	10	18.18%
textedit	2	3.64%
microsoft word	2	3.64%
notes.app	3	5.45%
vscode	7	12.73%
sublime or atomic or one of those	7	12.73%
textwrangler (remember that one?)	3	5.45%
<textarea> in the browser	2	3.64%
this thread	6	10.91%
Total:	25 votes

[Edit Poll (moderators only)]

chaosbreather: Dec 9, 2001; Wry and wise,
but also very sexual.

vscode is pretty great tbh and gets better alarmingly quickly

if you want to do vi, i recently found this: https://github.com/AstroNvim/AstroNvim which turns it into an kind-of-like-vscode which might be a good middle ground if you want to be a bit frustrated and not have vscode's "contemptible" graphical user interface but have something that approximates it

# ¿ Aug 4, 2022 01:25

Adbot: ADBOT LOVES YOU

# ¿ May 11, 2024 05:36

chaosbreather: Dec 9, 2001; Wry and wise,
but also very sexual.

akadajet posted:

how do you define ide?

a text editor knows about the text of text files, an ide knows about the entire project and the concepts and structures defined within and how they relate, and provide tools for analysing and changing that structure, which are all integrated.

vscode is a very bad ide, or maybe a series of quite bad ides, or a very good text editor

# ¿ Aug 11, 2022 10:34

chaosbreather: Dec 9, 2001; Wry and wise,
but also very sexual.

Zlodo posted:

in practice (when doing c++ at least): vs forces you to define a project hierarchy separate from the directory tree which also double as the build system definition

It's completely unecessary for an ide to work in this way and this is extremely impractical

In practice on large cross platform projects you don't want to use the built-in build system as your primary build system because it's poo poo so you end up with another build system (cmake or similar) that generates vs' projects and solutions

you therefore may have build files to edit that may or may not be referenced by the projects and become annoying to find and work with from inside vs (i often end up running vs code on the side for this reason)

when it comes to "changing the structure" aka refactoring on large projects you are usually better off turning intellisense anyway and installing some third party plugin such as visual assist because the integrated poo poo is unbearably slow (as in updating the database is slow and for some reason slows the UI down, at the most awkward of times)

my experience of using vs code for c++ on personal projects (not as big as the ones at work but not completely trivial either) is just better (and ironically i do also use Microsoft's c++ extensions in vscode, they just work better there)

there is absolutely nothing that makes vs code any less or any worse of an ide than visual studio, but Microsoft needs to justify the continued existence of the later and it being paid software (rather than folding every remaining specific vs tool into vs code and putting vs out of it's misery)

oh yeah vs isn�t an ide, it�s dog poo poo. jetbrains makes ides. I honestly didn�t know anyone ever used or thought about it ever

# ¿ Aug 11, 2022 15:15

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > Should I switch to emacs?