Form is emptiness, emptiness is form.
Still hung-over from Global Game Jam 2012 (mini-write-up later) when I went to the RailsInstaller site on a whim.
Noticed that it still isn’t using Rails 3.2. So I decided to update my own to be ahead again.
Hopefully this would be the last RailsFTW version (hoping Luis would be able to convince Wayne to include MySQL to RailsInstaller so I won’t need to this anymore LOL).
I’ve been doing some programming screencasts lately over my Youtube channel. They’re not really “screencasts” ala RailsCasts but more like informal streamed videos that you’d see in Justin.tv/Twitch.tv.
These screencasts were recorded in 720p so it’s a good idea to select a higher resolution then view the videos in full screen or the large player in order for you to read the code properly.
Here I code a hexagonal “game of life”-like cellular automata. Used Ruby, Gosu, and RSpec.
Walking through coding a simple Rails app. Bunch of technologies discussed like Twitter Bootstrap, Heroku, and git.
Going through Project Euler problems via brute force using Java.
Thanks to a Battlefield 3 Beta losing streak that I blame on my sucky internet connection, I’ve decided to update my hack-job of a standalone Windows installer for Rails.
Now there are two separate installers, a Ruby 1.8.7 + Rails 3.0.10 installer and a Ruby 1.9.2 + Rails 3.1.0. Here’s a table to give a quick comparison between these two installers with RailsInstaller thrown into the mix:
| RailsInstaller 2 | RailsFTW (Rails 3.1) | RailsFTW (Rails 3.0) | |
|---|---|---|---|
| Ruby version | 1.9.2-p290 | 1.8.7-p352 | |
| Rails version | 3.1.0 | 3.0.10 | |
| File Size | ~55MB | ~20MB | ~10MB |
| DB Adapter Gems | sqlite3, pg, tiny_tds (MS SQL Server) | sqlite3, mysql2 | |
| Additional Features | git, DevKit | – | |
| Internet Connection Required? | Yes | No (Bundler will fail to connect to server but new apps will still work) | No |
| Compiled by | Some of the biggest names in the Ruby community | Some random third world developer. LOL | |
Computer Science teachers have it easy. Every time a new semester rolls in, they can simply reuse the material they’ve been using for years.
As a teacher of a quickly evolving web framework, I do not have that luxury.
As I write this, less than 24 hours have passed since the Rails Core team released the new version of Ruby on Rails: version 3.1.0. This means that I now have to update my student manual (i.e. this document) for upcoming classes to use this new version. Having done that before when we moved from Rails 2.3. to Rails 3.0, I know how much of this document will be changed: sections will be gutted, swaths of code rewritten, and at least one new chapter would be added.
And, yet again, I will not be paid a single cent for those updates.
So instead of just letting this nearly obsolete document go to waste, I’ve decided to give it away for free.
Normally, I would’ve posted something like this a lot earlier. But work interfered so…
Anyway, since I won the event, I really don’t have an excuse not to do a post. Blow the cut are some of the lessons I (re)learned at the event.