Why does emacs not have a decent code browser? speedbar is

>>58505250
Have you tried this?
https://github.com/jaypei/emacs-neotree/

Also you may like dired-jump (built in) or maybe projectile with helm.

>>58505250
Here's the real reason:

Browsing is an inferior way of communicating with your editor. I realize this sounds pompous, but bear with me for a minute.

With packages like helm and ivy available, you can use fuzzy search to find the files/directories you are looking for. If you don't want to search, you can also use these packages to browse your directories in a list format, which is far easier than the traditional tree-style navigation that most editors and IDEs have.

My guess is that people came to emacs from other editors, missed their traditional tree-style navigation, and tried to replicate it in emacs. Then, after using emacs for a while, they realized that tree-style navigation simply isn't that great, and switched over to a package like helm or ivy.

It's the same reason why emacs doesn't have a good way of making tabs. As it turns out, buffers and windows are a far more intuitive and versatile solution than tabbed editing.

I strongly urge you to grab helm or ivy or ido-flx, you will move through directories much faster.

>>58506765
this

though i think helm is a piece of shit

>>58506970
Ivy is designed much better than helm imo, but there are so many third party packages that provide completion candidates through helm, that i'm stuck with it for now.

Here's a pretty good guide for making helm more bearable:
https://tuhdo.github.io/helm-intro.html

>>58506991
it's not that i don't know how to configure it, it's just that it's unbearably slow and slows down emacs SO much

so yeah i use ivy too, if i can't be assed to use ivy i just use the built-in ido mode