I’ve used Aquamacs for the past four years or so. It has its strong points.
But I’ve always been a little unhappy with its slow performance relative to native Emacs (I use a MacBook Pro), and its unique initialization and behaviors. I’m sure there are good reasons for every difference. But each difference, no matter how small, is a little more cognitive load. E.g., I never got used to M-x Info opening up in a new window somewhere on my screen…
Today, I decided to try Emacs for Mac OS X. Whoa! I love it! It’s Emacs, the whole Emacs, and nothing but the Emacs. Win!
I even donated $50 to the project. So there!
After my embarrassing post about anaconda, I’ve awakened a Jonesing for working again in Lisp. I think I’ll look for a project to contribute to — maybe start by fixing some minor bugs in an Emacs package, or something similar.
When setting up your .emacs to automatically add company-anaconda to your company-backends list, eval-after-load is your friend:
;;; Company, and Company backends.
(add-hook 'after-init-hook 'global-company-mode)
'(add-to-list 'company-backends 'company-anaconda)
I just discovered M-x balance-windows and balance-windows-area. GNU Emacs, you rule!
I’ve used identi.ca micro-blogging for the past five months. I’m switching to twitter.
I was involved with a number of projects at Fisher Communications until last month. Including building a Plone system to be its news sites’ in-house CMS. Our development environment and technology stack were open-source, with only a couple exceptions.
When I worked on our technology roadmap, an early consideration was how to distribute quick (lightweight) intra-team updates. Virtually the entire development team would be within the same building; of those, virtually all would be within one office. The CMS project would eventually reach 10 heads in dev, QA, and operations; plus content creation and advertising traffic control. Other dev or page layout individuals would be on other activities. For all of this, we needed a way to inform each other about daily activities. Daily stand-ups are used for this in a typical XP or Scrum team. (To be fair, stand-ups are used in many different development methodologies, but XP and Scrum have greatly popularized them in the mainstream technical media.)
Based on cursory searching, this chestnut first appeared on the web in 2006. I just came across it. (I disagree with the Visual Studio curve, BTW.)
Editor learning curves
I’ve been using SPE as my Python editor for a couple of years. It takes an IDE approach to the user window and UX model. I liked it, and I even donated money to its support fund.
But I’ve been an Emacs guy since back in the day. I was never fond of Emacs’ Windows integration, so I fell out of the habit of using it during my Windows years.
I’ve now discovered Aquamacs. Baby, I’m home.