April 18th, 2008
See this.
history | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head
4605 cd
3576 svn
2141 ls
1701 ruby
1308 cap2
1066 ss
978 rake
867 sshb
688 rm
635 mate
cap2 is just my alias for Capistrano 2 (I use both 1.x and 2.x, since I’m lazy to upgrade some old Rails applications, ss is my alias for script/server. sshb is a shortcut for ssh with a certain port number for SSH daemons (i.e. -p 22) that we use in Bezurk (you know, security through obscurity).
February 26th, 2008
Subscribers who read my blog for Ruby- or Mozilla-related posts should ignore this post, it’s another of those blogging as catharsis posts. To my defence, I haven’t done one of those for a really long time!
If you’re staying in Singapore and looking to try out the food at Shokudo Japanese Food Bazaar after it was featured in the local newspaper, my advice to you is, “don’t bother!” Why? In 2 words, horrible service.
Despite some positive reviews (yes, the decor is not too bad), my dining experience at Shokudo consisted mostly of getting the service crew’s attention (and failing spectacularly despite standing right at the counter) and being scowled at or avoided by most of the staff (which is not good, since being a bazaar-style restaurant, you needed to place your order at each stall manned by different members of the service crew).
My friends and I were speculating that either the staff got scolded that day (and reacted negatively to that), or they were just too stuck up because business was good. Either way, it was just terrible. When leaving, I even got rudely reminded that I’d left that one of those things they gave you to reserve a table. Did I mention the service was horrible? (Granted, there were 2 counters where the staff were attentive and actually quite friendly - this was at the macha drink stall and the katsu curry counter.)
What about the food? With such bad service I would say no one shouldn’t really care about the quality of the food - thankfully enough, the food is of a consistently mediocre level to even bother!
Has anyone had a similar experience at Shokudo, or was it just our unlucky day?
January 9th, 2008
It’s about 9 days too late, but I figure it’d be fun to just throw these out and see if anyone else enjoyed the same things I did in 2007.
PC Game of the Year
This has definitely got to go to Call of Duty 4: Modern Warfare. The single-player campaign was short but visually impressive and amazingly realistic. It was like watching a movie in most parts. And really, sneaking by Spetsnaz just a few metres away in sniper ghillie suits and was totally pimp. Multiplayer is real good fun too, I’m still playing it now (usually on GamingSA.com servers as ‘konata’).
Special mention: World of Warcraft (yes, I quit it ages ago, but it’s still good for the early part of 2007 when I was still playing casually).
PSP Game of the Year
Yes, I got a PSP just this year. And yes, Jeanne d’Arc is the best game I’ve played and completed in a while. For those who don’t know, Jeanne d’Arc is a very accessible Strategy RPG (SRPG) that is very loosely based on Joan of Arc. It’s much easier to play than Final Fantasy: Tactics or Disgaea: Hour of Darkness and doesn’t leave you constantly wondering about missing out on secrets. Highly recommended if you’re looking for an RPG-like game on the PSP.
I haven’t had the chance to play many other PSP games, but look forward to getting deeper into Disgaea: Hour of Darkness (and highly anticipating Final Fantasy VII: Crisis Core in March 2008).
Anime of the Year
2007 is the year I switched my anime tastes from mostly shonen anime (like Naruto and Bleach) to the seinen genre.
My favorite anime for 2007 (this is a tough one) has to go to Lucky Star. I even went through a prolonged Konata-ism phase and even had a printout of Konata saying “Relax” pasted right above where I sit in the office.
It’s therapeutic :)
2007 was a good anime year. Tekkon Kinkreet had an edgy, surreal drawing style but had a fantastic plot. I highly recommend it if you’ve missed it - it’s about 10 times better than your run-of-the-mill Princess Mononoke or Spirited Away type anime movies, in my humble opinion.
Potemayo’s moeblobs were just too funny to watch. Gochuko (below) had me LOL when she went around using tape to fix everything she sliced with her big scythe. At first appearances Potemayo may look like a kid’s anime but it’s really a work of comic genius for adults.
Genshiken 2 picks up where the 1st season left off and while the ending left quite a bit to be desired, on the whole it was enjoyable watching otakus cope with life (who knew it was so tough to get a job in Japan).
What about you?
What did you enjoy in the last year and more importantly, do you have any recommendations for an ani-otaku like me?
January 9th, 2008
Yup, it’s time for your weekly dose of the changes on edge Rails, more or less covered in the latest Rails Envy podcast. Using edge Rails is neither arcane nor terrifying, and hopefully weekly reports like these will allow you to take control of your own release schedule with your Rails apps.
This week’s report covers changes from 31 Dec 2007 to the day the podcast was recorded (6 Jan 2007).
Caching changes
Looks like most of the changes from the 2.1 caching branch have been
merged into the trunk. Some key points:
- memcache-client has been vendored (included in Rails directly). MemCacheStore works out of the box in Rails now, no need to install the memcache-client gem!
- The caching code has been refactored and moved into ActiveSupport (
ActiveSupport::Cache::*).
- Added
ActiveRecord::Base.cache_key to make it easier to cache Active Records in combination with the ActiveSupport cache libraries introduced in this changeset.
- Fragment cache keys are now by default prefixed with ‘views/’.
- Deprecation:
ActionController::Base.fragment_cache_store is now ActionController::Base.cache_store
Fragment caching now works in RJS and Builder templates
Yup, you couldn’t do fragment caching in non-erb views before - now you can.
Freezing Rails now automatically updates your Rails app
If you’re using edge Rails and use the rails:freeze:edge rake task, you probably usually forget to run (or maybe you’re not even aware of) rake rails:update to update your Rails app with the latest config/, scripts/ and javascript files from the version of Rails you just froze to. On edge Rails, the rake rails:freeze:edge task runs the rails:update task for you. +1 for convenience!
I prefer to use Piston so I’m gonna have to keep remembering to run my rake rails:update now and then!
Check out the related changeset.
Optimizations
Only 1 optimization in the past week worth talking about: the ActiveRecord::Base#exists? method is faster. It now uses ActiveRecord::Base#select_all instead of a more expensive ActiveRecord::Base#find that unnecessarily instantiates AR objects. (Check out the related changeset.)
Bug fixes
January 3rd, 2008
Yes, it’s a plug for myself and it’s shameless:
Whatever Zed Shaw may say about Rails its community, Rails has done a huge part in making web development fun again for jaded web developers (first-time web developers probably won’t be able to tell the difference), and more importantly, raising the profile of Ruby more than any other Ruby project/library/framework/tool ever did (and I’m sure we’re all constantly rolling our eyeballs at the new web frameworks that’re so terribly familiarly Rails-like). Hell, I bet at least 90% of Rubyists now wouldn’t even be Rubyists if they hadn’t come across the web framework that could 2 or 3 years ago. So yes I’d still be contributing to Rails so that it can make my life as a web developer easier, thank you.
I think I had about 18 accepted patches in December 2007 Rails Hackfest (a few of the patches were not attributed properly in the Hackfest due to technical issues with the Rails Hackfest site).
Probably the only significant patches were:
- Allowing a proc to be set for
ActionController::Base.asset_host (changeset 8421).
to_xml should not automatically pass :procs to associations included with :include (changeset 8258).
Of course Ruby 1.9 compatibility was a big deal in December 2007 since that Ruby 1.9 was targetted to be released on Christmas (changesets 8369, 8309, 8398, 8397, 8412). Yes, I know, Ruby 1.9 is a development release.
There were also broken tests to be fixed (changeset 8271), bugs to be fixed (fixing Array#to_sentence), and some refactoring (changesets 8343 and 8522).
And what would patching Rails be without random documentation fixes (changesets 8457, 8471, 8472, 8280, 8279, 8278, 8521). The API documentation always needs a hand, so if you see any outdated or incorrect documentation, or think you can improve them with better examples or whatever, just submit a patch (it’s easy and should take you all of 3 minutes).
This month’s hackfest has a terribly attractive top prize of a RailsConf ticket. Too bad I won’t be able to take part in this month’s hackfest since winners of past month’s hackfest are automatically excluded from the next’s. But maybe you can ;).