It comes down to workflow. For every individual that's going to be different, but ST's advantage is that advanced workflow is accessible to newcomers. You'll always find a tool that has particular features unmatched by others. I also use Vim and Crisp, and both are very powerful editors. I have also used Emacs. All of these I've used for many many years, I still use Vim and Crisp for particular tasks.
When I came to Sublime I was sceptical because in the beginning it was all about power, matching features and bending it to existent workflows from other editors. But the truth is, over time, I've developed new workflows around Sublime. Some I can match in other editors and some I can't, but in Sublime they're obvious and tightly integrated, whereas in others many aren't.
It's a personal choice, but I would allow your mind to stay open and stay focused on what the tool allows you to achieve, and how quickly and painlessly. For my purposes, coding in a multitude of languages and across different platforms, Sublime saves me a good deal of time from other editors. And for some reason, its aesthetics really help too. Sublime's approach is different: minimal UI, simple json-based config and quick and easy to tailor to your needs with plugins, themes, skins, shortcuts etc. After just a few days I was able to do all of these things and I didn't need to keep remembering how to do them. I love the fuzzy matching and how it prioritises completions for example. You can build your own knowledge base of keystrokes to match a pattern, and after selecting it a few times, it becomes the default. I love that kind of thing; the interface blends out and the editor just does what you want. I still prefer Emacs and Crisp's loosely coupled buffers and views concept, but you can achieve the same end in Sublime and in practice it doesn't affect my workflow.
For me, the biggest technical limitation of Sublime is the macros, specifically that they can only record text events and not things like search&replace or other editor actions. Crisp allowed me to build up complex repetitive commands into a macro, often including regex find etc. then repeat it over and over by hand, or X amount of times. I miss that from Crisp, and find myself going back there for certain tasks. That together with better code folding, virtual whitespace and proper line/column selection modes would make Sublime about perfect for me. Add onto that richer api's for sidebar etc. and a proper command mode for cherries on top. Lastly good performance on massive files, and the ability to monitor progress and abort any lengthy UI blocking operations, a PITA in sublime on big files.
The only other niggles with Sublime are documentation - could be better - and the developer responding to fixing things and community requests. Jon's done some great work and continues, I hope, to do so. But we do have these extended periods of silence, and some users are having issues with things not behaving quite as they should.