[edit]
It's missing a lot of the keybindings that made org mode so fast to use so not 100% there yet. Still awesome project and hope it gets continued investment like VIM mode for VSCode.
I'm not even scared off, but I won't use Emacs because it doesn't have tabs. I know about the alternatives presented, but I just want tabs. I find it funny that the kitchen sink "Eight Megabytes and Constantly Swapping" Emacs doesn't have a built in tab implementation while the supposedly small Vim has one :)
I normally use IntelliJ with two panes open, and about 120 tabs between the two of them. But because IntelliJ tabs can't scroll and Java filenames are long, the tab I want to switch to is never visible, and the tab list dropdown is painful to scan. C-n and C-S-n are what I end up using.
And for the browser, I use tree-style tabs. The hierarchy keeps related tabs together, and I can collapse when I do a context switch. The fact I can see all the (top-level) tabs at once in a long list means spatial memory works better.
In emacs, I use Helm and Projectile, bound to F11 and F12 for buffer and project searches. I've bound buffer switching to C-prior and C-next (those are PgUp and PgDown), and since the buffer order is basically a LIFO of whatever buffer you jumped to, the buffer you're looking for is usually within easy scrolling reach.
I also use a really big amount of open tabs in my web browsers (I group them in different windows). On IntelliJ, though, I use tabs as my "working area", and it never spans more than 8-10 files. It helps me keep my commits small and focused, never touching too many files.
PS: You can disable tabs entirely by setting tab placement to "None".
I can't hide the tab bar because I need it to control which pane a file is showing in. E.g. I want test and implementation visible at the same time; this usually requires that I drag one or the other tab to the other pane, because IntelliJ brings tabs to the front of whatever pane they're already living in, rather than moving them to the currently focused pane.
I do my commits from magit in emacs. I generally don't commit at all until I've done something somewhat significant, but I'll break it down into commits on a diff hunk by hunk basis, which magit makes easy. I don't use the IntelliJ SCC tooling.
I especially don't like tabs in IntelliJ Idea: I never (except the cases when I want to detach one to a separate window) actually use them, every time I want to switch to a particular file in a project I choose it in the project tree in the left panel, the tabs only pile up atop of the editor pane and annoy me so I close them every now and then.
I made a very simple webextension that disables tabs in firefox, so that I can use my window manager's tabs instead. I've been using it since the stable release of Firefox 57. http://static.adrusi.com/notable.html
And I use Windows so a fancy WM is almost out of the question.
Also bear in mind that an Emacs session for many users lasts for days or months (I just checked---the Emacs server session running on the machine I do most of my work on has been running since last November, and I currently have more than 50 buffers open). In that sort of use-case, tabs don't make any sense, but tools like Helm and Projectile make it quite efficient and easy to navigate among your files and buffers.
I don't have any great need or investment in convincing others to use Emacs. However, people might want to consider that, while new users often detest it, those who do spend the time to actually learn it---which, to be honest, probably requires an investment of time and focus few are willing to offer---then refuse to ever use anything else. Surely they're finding something of value that casual users aren't encountering.
Complaints about Emacs invariably seem to be some variant of "it's not like my favourite editor, which has feature x, so I won't use it". Which always sounds to me a lot like an experienced car driver refusing to try a helicopter because it doesn't have a steering wheel.
Also, with Vim you can mix and match tabs and splits to have many files open at the same time. You also have buffers, which I believe are the exact equivalent to Emacs buffers, you can have a gazillion buffers open at the same time and only a few visible.
I've seen some vim workflows using only buffers instead of tabs, but they required doing :ls :b buff_number to switch to another file, which seems worse than looking at your tabs and repetitively do "gt" to access the corresponding tab.
I could use the ctrlp plugin or one of its alternative to fuzzy search on the file name instead of manually changing the buffer, but I still don't see a real benefit over using tabs. I guess it makes sense with really big projects where you have to open more than 10 files at a time.
(I don't use file marks for this purpose any more. I got annoyed at how file marks saved and restored the cursor position within the buffer, so I wrote my own vim plugin to use a similar "map this buffer as A", "go back to buffer A" system, without saving/restoring the cursor position as well. I never really properly released it, but feel free to give it a try if you feel it would scratch an itch for you. It's over here: https://github.com/vectorstorm/vim-spacelanes )
To underline that, what folks have working for them is working for them. Sometimes, it can help to try and push out of a comfort zone. But, there are no guarantees. To that end, try what others report as working for them. But don't sweat it.
That said, instead of tabs, I recommend getting used to something like helm. When you have 150 files open even windowing and LRU won't help you enough. Switching to buffers by typing in a few characters of their name and then hitting enter can be done open-loop and not having to find things with your eyes is a major speedup.
With Emacs anything is possible. You don't have to settle for buffers. There is also speedbar for a tree-based view.
But Emacs eventually won, and I’m glad that it did. Searching for a buffer with a few keystrokes is way better than flipping linearly through a huge stack of arbitrarily-ordered tabs.
(Plus, a minimal interface just looks cooler.)
Maybe if window managers were substantially better.
As for Emacs, "open files" mean nothing for me as an end user. The editor could hide that feature away and I would still work in the same way. I just use projectile and neotree to switch to the file I want. And efficient as that may be, I still lack a visual cue of what I'm doing. Tabs do that job perfectly.
Another thing to consider, how often do you need to look at the buffers, but not change to another buffer?