Do we know exactly what it’ll be yet? Not quite. We have some hints… but until it’s released… we’ll continue to speculate.
While I am not one to make predictions—I do have a few theories about what Atom will not do for us. (if you’re looking for a new business idea… feel free to snag any of these)
1. Atom Editor will not make it easier to code while in the shower. While I would love to take advantage of putting my thoughts to code while letting my conditioner do it’s thing… I don’t believe they’re trying to solve this problem (yet).
2. Atom Editor is not going to make it difficult for me to produce shitty code. To date, nearly every code editor on the market is focused on making it easier to produce code…. good AND/OR bad. Where is the editor that tells us to quit while we’re head. “Are you serious, Robby? Have you seen what you’ve been writing today? Just stop. Go outside. Take a break and try again tomorrow.”
3. Atom Editor will not bring synergy to developers.
4. Atom Editor will not change the music playing to compliment the coding problem that I’m faced with. If my tests aren’t passing… I wish my music would keep me calm and focused. This is not a time to start playing WHAM! (…or maybe it is)
5. Atom Editor will not bring about peace in the Emacs vs Vim wars. We are going to have to let them sort a peace deal on their own.
6. Atom Editor will not have integrated CVS or Subversion support when it is released.
7. Atom Editor will not promise the world to you like Visual Studio.NET did back in 2002. I remember their demo videos and it seemed like the development world was about to change! I never would have guessed that come 2005, I’d be in love with something as simple and fancy-feature-less as TextMate.
8. Atom Editor will not just be a clone of Sublime Editor. Github has too clever a team for that objective.
What are you confident that Atom Editor will not be?
8 for 8!
funny how Twitter warned me that a bunch of my friends at GitHub are all a sudden interested in https://t.co/cb52btuPZe— Matt Aimonetti (@mattetti) February 26, 2014
...which leads us to
Initial sources suggest that will be one of the biggest app releases of the year.
It’ll be loved by many. Hated by some.
As we learn more… I will try to keep this updated. Here are a few “screenshots” people have posted on twitter.
Some animated gifs:
SOON.— Tom Preston-Werner (@mojombo) February 26, 2014
You might consider following @AtomEditor on twitter.
Earlier today, I noticed that we now have over 500 developers from around the globe who I have accepted pull-requests from1. That is so fantastic.
Thanks to each and every one of you who has helped make this project so wonderful for others. :-)
1 This number could be a lot higher if I spent more than a hour or two a week on this, but I’m a big fan of slow and steady… a good number of the open pull-requests are themes at the moment.
Welcome to what seems like my tenth installment (actually, it’s the fourth) of showing you how I setup my development environment on a fresh OSX install. In this case, I’m actually getting a MacBook setup for a new employee with Snow Leopard.
Over the years, I’ve evolved these following steps and they’ve helped our team maintain a consistent and stable envirnment for Ruby on Rails development. I know that there are a few other ways to approaching this and I’m sure you’ll get similar results, but this approach has allowed me to maintain a hassle-free setup for the last five years.
As with all things… your milage may vary.
During this initial phase, we’re going to install the primary dependencies and setup our environment.
The first thing that you’ll need to do is install XCode, which almost everything depends upon as this will install developer-friendly tools for you. Apple has been kind enough to ship this on your Snow Leopard DVD.
Go ahead and install XCode from the Optional Installs folder.
(might require a reboot)
You can also download it online.
Now we’ll install MacPorts, which the web site describes itself as, “an open-source community initiative to design an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the Mac OS X operating system.”
As I’ve said in past versions of this guide, this tool is about to become one of the most important tools on your operating system. It’ll be used time and time again to maintain your libraries and many of the Unix tools that you’ll be using. If you’re from the Linux or BSD world, you are likely familiar with similar tools… such as:
You’ll want to download the latest stable version from http://www.macports.org/. Once downloaded, you can install it.
Once this is installed, you’ll be able to use the
port command from your console.
Let’s test out your MacPorts install by installing a useful tool called wget, which we’ll use to install oh-my-zsh.
sudo port install wget
Git and Subversion
Every development environment should have some source code management tools available. We’ll install both of these with one command.
sudo port install git-core +svn
This will install git and subversion.
Oh My Zsh is the most amazing thing to happen to shells since… well since I said so. It’s one of my open source projects that I encourage you to give a whirl.
wget http://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | sh
That’s it. The next time you open up your terminal, you’ll be running zsh with a bunch of stuff available. For more information, visit http://github.com/robbyrussell/oh-my-zsh.
Terminal theme (optional)
I never understood why the icon for Terminal has a black background but when you start it up the default theme is black on white.
Anyhow, I’m a fan of the the dark background. To change this, open up preferences in Terminal. Select Pro, then click on the Default window so that this sticks around.
Let’s now open up a new Terminal window..
You should be looking at something like this:
Much better… let’s continue.
We’re now going to start installing everything we need to get this running.
First up, Ruby.
Snow Leopard includes Ruby and Rails already installed, but we’re going to back these up for a rainy day. Just issue these commands:
$ sudo su - Password: :~ root# mv /usr/bin/ruby /usr/bin/ruby.orig :~ root# mv /usr/bin/gem /usr/bin/gem.orig :~ root# mv /usr/bin/rails /usr/bin/rails.orig :~ root# logout
Now we’ll go ahead and install a fresh copy of Ruby and RubyGems via MacPorts.
sudo port install ruby rb-rubygems
You should now see something like this for a bit…
Let’s watch a video about bumble bees.
When it finishes installing, you should check that Ruby is available to you and installed in
We’ll also take a second to create a symlink for this as some tools seem to rely on
/usr/bin/ruby being there.
sudo ln -s /opt/local/bin/ruby /usr/bin/ruby
Great, let’s move on.
Now that we have Ruby installed, we’re going to take a quick detour to setup Passenger with the Apache server already available on your machine. I’ve been a big fan of using Passenger for your development for over a year now.
sudo gem install passenger
Once the gem is finished installing, you’ll need to install the apache2 module with the following command:
It’ll ask you to continue by pressing Enter. At this point, it’ll check that you have all the necessary dependencies and then compile everything needed for Apache2.
Now I’ll force you to watch a highlights reel of Fernando Torres… the best striker in the world!
The passenger install will then show you this output, which you’ll want to stop and read for a moment and highlight the following:
Then using vi or emacs, you’ll want to create a new file with the following content:
Then paste in the following (what you highlighted and copied above.)
LoadModule passenger_module /opt/local/lib/ruby/gems/1.8/gems/passenger-2.2.9/ext/apache2/mod_passenger.so PassengerRoot /opt/local/lib/ruby/gems/1.8/gems/passenger-2.2.9 PassengerRuby /opt/local/bin/ruby
You’ll also want to include the following below what you just pasted.
# Set the default environment to development RailsEnv development # Which directory do you want Apache to be able to look into for projects? <Directory "/Users/ryangensel/development"> Order allow,deny Allow from all </Directory>
You’ll want to quickly start up your web sharing, which will start Apache2 up via your System Preferences.
Simple enough… moving forward.
Passenger Pref Pane
To make things as simple as possible, I’d encourage you to install the Passenger Preference Pane (view this post for a download).
I have a directory named
development/ in my home directory, which is where I end up storing all of my projects. This should match whatever you put above in the apache configuration (
mkdir development; cd development;
Installing Ruby on Rails via RubyGems
Now we’ll use RubyGems to install the latest version of Ruby on Rails (and all of it’s dependencies).
sudo gem install rails
While this is installing, you can watch a video from my old band that ended around the time that business started picking up for Planet Argon.
Great, let’s test out the install of Rails…
Test Rails and Passenger
In your development directory, let’s quickly a new Rails app…
This will generate a new Rails application in a
Now open up the Passenger Preferences Pane and add this directory as a new application.
You should now fire up your browser of choice and head to
http://testapp.local. If all has worked, you’ll see a, “Welcome aboard” screen from the Ruby on Rails application.
Assuming that this worked for you, let’s take a quick break to make some tea…
In this last phase, we’re going to install a few database servers and corresponding rubygems so that you can get to work.
At this point in time, the current stable version of PostgreSQL via MacPorts is 8.4.x. Let’s install that now…
sudo port install postgresql84 postgresql84-server
Once this finishes compiling, you’ll need to run the following commands to setup a new PostgreSQL database.
sudo mkdir -p /opt/local/var/db/postgresql84/defaultdb sudo chown postgres:postgres /opt/local/var/db/postgresql84/defaultdb sudo su postgres -c '/opt/local/lib/postgresql84/bin/initdb -D /opt/local/var/db/postgresql84/defaultdb'
Assuming that you want PostgreSQL to always be running, you can run:
sudo launchctl load -w /Library/LaunchDaemons/org.macports.postgresql84-server.plist
...and to start it right now, run:
sudo launchctl start org.macports.postgresql84-server
Before you can start using it, we’ll need to make sure that the PostgreSQL executables are available in your shell path. Since you’re now using oh-my-zsh, you’ll want to edit
~/.zshrc with your favorite editor.
Just append this to
export PATH= line in the file.
Your PATH might look something like the following now:
@# Customize to your needs… export PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/local/lib/postgresql84/bin@
Setup database user
To setup a new database (with superuser credentials), just run:
createuser --superuser ryangensel -U postgres
We’ll now test creating a database:
Let’s test that we can access it…
➜ ~ psql test_db psql (8.4.2) Type "help" for help. test_db=# \q
Great, let’s drop it now.
➜ ~ dropdb test_db ➜ ~ psql test_db psql: FATAL: database "test_db" does not exist ➜ ~
Okay, we’ll now install the library that will allow Ruby to talk to PostgreSQL.
sudo gem install pg
Voila… let’s move on to the inferior database…
We’re going to run through the installation of MySQL really quickly because you might need it.
sudo port install mysql5 mysql5-server
This took ages on my machine… so let’s watch a video.
We’ll now setup the database and make sure it starts on system boot.
sudo -u _mysql mysql_install_db5 sudo launchctl load -w /Library/LaunchDaemons/org.macports.mysql5.plist sudo launchctl start org.macports.mysql5
Let’s test that we can create a database now (and that it’s running.)
➜ ~ mysql5 -u root Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 Server version: 5.1.43 Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> create database test1; Query OK, 1 row affected (0.00 sec) mysql> \q
Great, we’ll now install the library that will allow Ruby to talk to MySQL.
sudo gem install mysql -- --with-mysql-config=/opt/local/lib/mysql5/bin/mysql_config
That should be it!
Phase Four, next steps
Okay… so we’ve installed XCode, MacPorts, Ruby, Rails, PostgreSQL, MySQL… and I’ve also got you to switch your default terminal shell from bash to zsh. You might take a look over the available themes for Oh My Zsh so that you can personalize your terminal experience even further.
You also now have a handful of gems installed as you can see with
This is the fourth version of this guide and I’ve appreciated the hundreds of comments, questions, and emails that I have received… let’s not forget all those beers that people buy me when I’m at conferences. :-)
I hope you have found some of this useful. If you have any problems and/or questions, don’t hesitate to post them in the comments section below.
1 comment Latest by Jason Green Fri, 29 Jan 2010 15:11:02 GMT
Here is a sampling of some of the themes that you can use out of the box with Oh My Zsh.
Oh My Zsh is much more than a collection of themes for your zsh config. It’s a way of life1.
Also, be sure to follow ohmyzsh on twitter now!
1 well.. at least while you’re in the terminal. ;-)
1 comment Latest by Justin Gallagher Sun, 03 Jan 2010 23:11:32 GMT
To track an event with Google Analytics, you’d need to trigger something like:
pageTracker._trackEvent('Button', 'Click', 'Get in touch');
As you can see from our code earlier, in development, the
_trackPageview() and handle it appropriately.
This class works with the following logic:
- if google analytics is loaded, pass the parameters to the real
- if google analytics is NOT loaded, output the information to
console.log()for debugging purposes
And in our production environment, we can see that this was sent to Google Analytics.
We’re able to do this by initializing the GoogleAnalyticsProxy class and calling these functions through it. For example:
_gap = new GoogleAnalyticsProxy(); _gap._trackEvent('Video', 'Play', 'Homepage video'); _gap._trackEvent('Video', 'Pause', 'Homepage video'); _gap._trackEvent('Button', 'Click', 'Call to action X');
You’ll see that we’re just calling
pageTracker. We then replace all the instances of pageTracker (except where it is defined in the google analytics code block they provide you). You’ll find this located near the bottom of our
We now have
_gap available throughout our project and can call
_trackPageview() with it. Note: You can use any JS variable name that you want, _gap is just what I went with.