I feel like Emacs is a huge mess right now.
for the longest time emacs used language modes to provide support for different programming languages. this ended up being a mess ofc. because everyone implemented modes for different language mostly from scratch. for example C mode is around 20k lines of elisp that was piled throughout the years by emacs developers hacking on it and adding to it to make it somehow work.
the situation is even worse for javascript. since the built in js-mode was terrible. and people made a gazillion different javascript mode for emacs. some of them built on top of the built in js-mode, some of them aren't. we have now js-mode, js2-mode js3... tide, web-mode, rjsx etc...
recently with the introduction of lsp and tree-sitter and as more editors started integrating those and building their language support on top of them. several emacs packages for lsp and tree-sitter eventually appeared. (lsp-mode and tree-sitter). and in the last two releases emacs integrated an lsp client and treesitter support into core emacs.
this made the situation even more moronic. since now on top of the normal emacs modes we have tree sitter modes. we have js-mode and we have js-ts-mode, we have c-mode and we have c-ts-mode etc... pretty much for every normal mode there is a treesitter mode that uses the treesitter parser (which you still have to configure manually). more treesitter modes are being developed recently and will be included in future emacs releases.
this is great. and i hope in the future all language modes use tree sitter for parsing and providing syntax highlighting, handling indentation etc...
and people are already writing packages for semantic navigation and selection that uses the built in tree-sitter features.
but for now. non of that shit is ready. emacs is stuck in this limbo. where some stuff are still done the legacy way. and some stuff are done using tree-sitter. a lot of the treesitter modes are still built on top of the old modes.
>right now
checked
true. it was always messy. but at least things were more consistent
sacred thread
on top of that we are seeing a shift away from large packages that implement their own stuff from scratch like helm, ivy, company, etc.... to more minimal modular packages that make use of native emacs features like vertico, corfu, eglot etc...
this is also a welcome change. but some of those newer packages aren't as mature as the old alternatives. so we are stuck in limbo.
I feel like we need another 2 or 3 years for the new features to mature.
which is a shame because neovim already managed to do that and create a somewhat functional and modern ecosystem.
although I am not a huge fan of vim/nvim
>which is a shame because neovim already managed to do that and create a somewhat functional and modern ecosystem.
Neovim is still a scuffed Emacs in every respect but LSP performance, and even that is being nicely addressed in Emacs 30.
>being bicely addressed in emacs 30
?
something new or just eglot?
New JSON parser
and how is that better than the one that got baked into emacs 27
NTA but there's an lsp-booster package that makes JSON parsing 4 times faster:
https://github.com/blahgeek/emacs-lsp-booster
with the new json parser it can apparanlty parse json faster than it does bytecode like it does with those booster packages
are they gonna use simdjson?
apparently jansson is mid as frick, i haven't tried 30 yet but apparently the performance gains are huge
This is why I never switched from vim. Emacs feels like the vscode js shitter mess just older.
>but some of those newer packages aren't as mature as the old alternatives
the frick are you talking about exactly? vertico, consult, corfu & cape are already more than stable and easily hackable. what is missing in them that stops you from producing code?
>so we are stuck in limbo
you're the only one stuck in a limbo of ineptitude, sorry but Emacs is not for you, stay with vim / VSCode
>i hope in the future
Big mistake right there
>neovim
Bigger mistake right there. Use vim, neovim is a shit.
Just use vscode, it's what emacs would be if it started from scratch now.
That's just the nature of open software, if you want consistency just use something else.
If you're crying over having too many options this thing clearly isn't for you, and there's nothing wrong with that.
not mad or anything.
yes, there are many options. but non of them work properly
lol this. too many digits
>emacs
>for when you need to do anything except be productive
I only use emacs because it has magit.
what's so special about magit? same goes for any editor/ide git package, what exactly is the point? what does it do that the git cli can't do?
>what does it do that the git cli can't do?
Technically nothing, but it's extremely comfy and has basically every feature you will ever need. Unironically it's better than commercial VC tools.
is it just a matter of familiarity, or syntax making things simpler, or something along those lines? i'm trying to wrap my head around why people wouldn't just use the git cli.
Just try it for a bit. You'll get the appeal.
i don't use emacs and i don't plan to. i use nvim, but i've never understood the git plugins for that either. tried a couple, and it just seemed tedious to learn new syntax for something i already know how to do with the cli. i really don't understand the appeal at all.
these tools offer better ui for scrolling through other people's repositories. instead of typing git commanss you press a few keys/click gui, and it shows you the log with diffs, branching indentation, who did what, allows quick jumping between commits and versions of files right in your editor/ide. le interactivity. they're not a ui to a git server and its functionality like issues/pull requests/releases though, so they're all incomplete and troony.
ok that makes sense, thanks anon
I don't know about magit but fugitive-vim is my favorite git interface because it's designed around the git CLI enhanced by vim buffers abd6 motions and the magic of Tim Pope.
if you combine git-timemachine and magit with a good keybinding setup, you can achieve a much faster workflow than you could by just typing CLI commands, to the point that you'll do stuff with your repository that would never occur to you to do on the CLI because it would be too time-consuming.
how is it a huge mess? You don't need any of the stuff you listed to write code.
How is guile coming along in relation to emacs? Is it worth learning?
just use vscode
its literally boobs sideways what a massive oversight
its allah
M-x jihad-mode
...
uhhh ummm....
>using lsp-mode in fricking 2024, almost 2025
homie pls
I use eglot personally
but lsp-mode is still better than eglot in some places
Chill out bro it's fricking april
works on my machine
Emacs is still the funnest editor. Enhancing the editor on the fly by writing and evaluating Elisp is an amazing feeling, and I wish more things had this ability.
>number of times you've done this in the last 10 years: 1
And it was a base option that you could enable in VSCode too. But at least you look like an oldgay, right? moronic npc nocoder.
You call me an NPC, but here you are bragging about how little imagination you have.
You write like a troony
have a nice day
You write like a Redditor.
Let me guess r/the_donald brought you here?
tl;dr: I'm too moronic to write my own Emacs configuration.
vi
mg
you don't need more
get to work tinkertroon
>vi
stopped reading here
stop dilating your 'figs and get to work, tinkertroon
Seethe and cope wagie cuck.
>mono-neuronal pov
why does this image have a different hash every time it is posted
look up optipng
emacs still sounds very sex to me tbh
once in a while I'll download it and play around but vscode just gives too much out of the box
problem with autistic software is that they don't get the defaults right
@100048550
>Just use vscode, it's what emacs would be if it started from scratch now.
No.
if you like emacs come to