Our last package roundup was in May, before Atom 1.0 was released, so we decided to share a few new packages we’ve tried out since then. As always, you can check out the full list of packages and themes on Atom.io.

Update: Atom has switched to the Contributor Covenant since this was originally posted. See atom/atom#8312 for more details.

Over the few last months, the Atom team has been working hard to improve the editor performance and deliver you an even greater experience. Today, I am going to shed some light on a few techniques we used to speed up the rendering process.

As we’ve focused on improving Atom’s performance over the past few months, one interesting optimization challenge has been a construct called markers. Markers allow a logical region in a buffer to be tracked, even as the contents of the buffer change. For example, the marker represented by the green highlight below continues to cover the same region, even as the text is edited:

The Atom team is leading a workshop at this year’s OSCON in Portland, Oregon! We’ll cover the basics of developing new packages, and be available to answer questions about working on Atom core. The workshop is at 9AM on Monday, July 20, and if you’re attending, we’d love to see you—if you’re not attending but would like to, early pricing ends on Thursday.

As of Atom 0.206.0, deprecated APIs will not be available by default, and packages using deprecated APIs will no longer be loaded.

The last package roundup was back in February, so we wanted to highlight a few packages we’ve been trying out recently. Let us know if you’ve been working on or using interesting packages which haven’t been featured yet!

You’ve got to look good in the future. We know this, so we’ve surveyed time-travellers from the future and hired a team of designers to invent the next wave of fashion.