I switched over to Atom a few months ago and haven't gone back. The speed at which Atom is being developed is great and the plugins so far have been fantastic. All of the tight github integration has really sold me.
What about performance? I've heard that Sublime is still much faster and less laggy than Atom, given that Atom is created with Electron (which is more a hybrid web view than a native app).
It was definitely worse a few months ago. It's gotten much better.
Still too slow to be used on large projects.
I use Atom for many reasons, but sadly the performance isn't one of them. It still can't be compared to SublimeText yet. There's a noticeable delay when you type and opening and closing files and rendering syntax highlighting and so on all takes longer.
It's by no means slow, but it's not instantaneous like ST.
The stability of Atom is a deal-breaker for me. It constantly crashes on projects with a lot of files.
Or you could just do yourself a favor and use Atom instead!
Couldn't be happier with Atom. Virtually all the functionality of Sublime with less headaches. Auto updating packages & even less resource intensive (for me at least). I still need to spend some time with Brackets, but for now Atom is my go-to.
I only recently heard of Brackets but it looks pretty sweet, too. I'd love to see a marriage of the two, if only sighs wistfully
I'm actually kind of bummed about this. I was hoping that when Will Bond was brought on board, Package Control would be built into ST3.
Does anyone know why the shortcuts on that site displays like this on my Mac: .
Seems like I'm missing those glyphs, but only in Open Sans? I can copy-paste it here without problems: ⌘
It's working on my machine.
Which web browser are you using? It working on Safari 9.1.1 and Chrome 50.0.2661.102 for me.
Turned out the problem was locally installed Open Sans, as Jonathan pointed out below.
I have the same issue. Do you have Open Sans installed locally? When I disable the local font and refresh the page, it works fine. Haven’t figured out how to fix it with the local version enabled, though.
Actually yes, I had it activated in Typekit. Deactivated it and now it works like it should. Strange.
I'd guess your local version doesn't have that character — or maybe that character at that weight & style — something I've seen a few times on TypeKit.