Full stack web developer, interested in all the things, but especially the web, code, design, Linux, OS X, PHP, WordPress, JavaScript & robots.

Tagged: editors

CodeMirror image/svg+xml

CodeMirror is a versatile text editor implemented in JavaScript for the browser. It is specialized for editing code, and comes with a number of language modes and addons that implement more advanced editing functionality.

I came across this today whilst searching for some information about syntax highlighting. I haven’t got a use for it at the moment, but it looks like a nifty editor and I’d definitely like to have a play with it.

I’m dumping Atom and moving back to Sublime Text

Back in May, I switched from using Sublime Text to Atom. I’m now moving back to Sublime. Atom is not a bad editor, I actually enjoyed using it, but in comparison to Sublime, it’s a power-hungry slouch.

I spend the majority of my working day in my editor and I constantly switch between projects, this meant that I really noticed how slow Atom was at starting up. Sometimes I’d click Atom’s app icon and wait, and wait, and wait. In comparison, Sublime starts almost instantly.

The poor performance was also noticeable when dealing with large files. I often work with large CSV files and they weren’t a pleasure to work with in Atom. Sublime on the other hand, seems to handle large files OK.

Lastly, Atom drained the battery on my 12inch MacBook incredibly quickly. In fact, it drained the battery so quickly, it made me feel uncomfortable. Also, on my Core i7 (Quad Core 4GHz) Hackintosh system, it would make the system fans spin-up and hum, which also made me feel uneasy.

With all that in mind, and considering that Atom and Sublime are on par for the features I actually use, it was a no-brainer for me to switch back to Sublime. I’m not sure what efforts are being made to make Atom more performant, or whether it’s even possible given its Electron core, but I think it really needs some attention. Meanwhile, I’m super-happy to be using Sublime again.

Switching from Sublime to Atom

A couple of months ago, I considered giving Atom another try. I didn’t. Yesterday, a tweet by David Walsh caught my eye and led me to install Atom, again. What can I say, I’m a sucker for sparkly things.

This morning, I removed Sublime Text from my system in an attempt to force myself to use Atom. By doing this, I’m hoping I’ll discover its features a lot quicker than I would if I was just dipping my toes in.

Anyhow, I’ve been using it for a couple of days now and first impressions are good. I’m sure it doesn’t start-up as quickly as Sublime, but once it’s running, it’s quick enough. One thing that I did find off-putting was the default colour scheme used for syntax highlighting. The thing is, there is nothing wrong with it, it’s just that I’m not used to it and I didn’t realise quite how important the colours are, until they changed. Not that it matters, I did a quick search and found this Monokai theme, installed it and everything was back to normal, well, normal for me.

It’s early days, but so far I’m enjoying the Atom experience — I’ve been using Sublime for years and the change is quite refreshing. I’m now looking forward to finding out what Atom can do.

Ten essential atom packages for web developers image/svg+xml

Github’s atom is getting popular very fast. A lot web developers are slowly moving over from sublime text. These Packages should help make your life easier.

I’m still using Sublime Text 2, it does the job and it’s super stable. I’ve tried Atom a couple of times, but it always feels laggy and slow in comparison to Sublime. Maybe it’s time to give it another try.