I occasionally get the opportunity to revisit code and rewrite applications i’ve written previously. Without fail i can always tell which of the applications was being used by me directly and how often i was running it, if not by the quality of the code… by the progress monitor i implemented. There are usually three monitors, and i can see each of them standing as a checkpoint to the next.
- Iterate through with some character dropped on the screen
- A Percentage completed bar that updates
Each one has its benefits and usefulness, so i figured id take a moment to step through each of them and where i use it, as well as how i coded it for the latter two.
I nearly forgot yesterday that Ruby has a train following it about. It has been growing in popularity over the last few years as it has become more and more well known as the language used behind a growing number of applications, such as campfire for instance. I have no complaints about it though, its actually a very useful language. My problem, as is often the case, falls on ignorance and the terrible practices of fearing languages.
When someone approaches me and asks me if I know Ruby on Rails I have to answer, quite politely the first time, no. I don’t know Ruby on Rails any more than I do QCodo, PHPCake or any other of the dozens of web frameworks. The attachment of “on Rails” to Ruby has really ruined, at least in my mind, the possible momentum that could be enjoyed by Ruby as has been enjoyed by other languages like, Perl or Python. The fact that these later languages names begin with the letter P should not lead anyone to believe that they are P-opular. All of the languages that I have experience with have their place in my heart and a place in my development practices. From my point of view, pinning “on Rails” onto Ruby weakens the message that many of us have already taken to learning.