It'll Never Fly

Clever… not good, but clever.

If you’ve enjoyed the last month and a half or so of this blog, I’m happy for you. The reason I’ve had the time to make multiple posts a day and make posts at 3:00 in the morning is because I haven’t had a job for that time. I didn’t mention it before because I didn’t want to talk about it. I still don’t want to talk about it. It’s over. It’s done with. It’s time to put it behind and move on. The only reason I’m bringing any attention to it now is because the frequency and amount of posts I’ll be making likely will be changing soon (think “less”).

I start a new job Monday. It’s still computer related, still programming related, but it’s a slightly different approach to working that I haven’t done before. It’s only guaranteed for about 6 months or so, but it’ll give my a better idea of what I want to do.

I’ve got a back-log of videos on YouTube to post about, but I likely won’t be “scooping” anyone, plus I finally figured out how to automatically post my del.icio.us bookmarks on a daily basis, so the blog might turn into a link log for a little while until I settle down again.

Just thought I’d warn all y’all.

Very interesting use of SQL to solve the popular number puzzle game.

read more | digg story

I’m giving Akismet a try. Since I’ve started my blog on WordPress, I’ve had 2788 spam comments. Not a lot considering how many I get in my inbox. Hopefully, I won’t have to hand pick spam to filter out anymore. The more I can do now to make me do less later is a good thing.

I mentioned how I’ve been checking out Ruby. I’ve been considering 4 possible candidates: TextMate, Xcode, Eclipse, and jEdit.

First runner-up is TextMate. Its claim to fame is that it was used to demo Rails in the infamous Rails Academy video. It’s a native editor (so it won’t have all those unexpected behaviour gotchas). I really like how TextEdit feels when I’m working in it. It’s got all the important features a modern text editor used for programming requires nowadays. I’d have ended this blog entry right now if it weren’t for one nagging problem. Its code-completion/code-sense/intellisense/whatever, is really rudimentary. It works, but it could be so much better. If I had to compare, I’d say it’s like the T9 predictive typing on cell phones: utter crap, but the best they’ve got for the price you’ve paid. I anxiously await the addition of a fuller-fledged completion system.

Hang on… I know Xcode now has code completion, and I’ve heard it plays nice with Ruby. How good could it be? Actually, not that bad. It’s native. I’m somewhat already familiar with it. It’s got syntax hilighting (albeit not the best), and it has a better code completion system than TextMate.

Neither one has the optimal code completion system, however. Neither one pops up suggestions upon hitting a period, for instance. TextMate won’t give you any completion, or even hint that it can, unless you begin to type some characters first. And even then, you still have to know ahead of time what you want to complete. Xcode’s is much better, but only about 75% to 80% of the way there. Xcode’s is a little better to deal with in that it offers suggestions before you begin to type (making it better than TextMate), but suggests every possible symbol in its lookup table regardless of it being valid in the current context or not (making it worse than TextMate).

Neck and neck in the non-native arena are Eclipse (with RDT) and jEdit (with the Ruby Plugin). jEdit was the winner, but only by a slight margin, and I think it was because I could do word selections in it, but not in Eclipse. I’ve heard good things about code completion in Eclipse, but I couldn’t get it to work. Maybe that’s what the oddly worded “Note:Currently, RDT is not supporting code completion for core libraries” phrase means in the Ruby on Rails Wiki. Eclipse’s biggest problem is that it felt like an IDE with a text editor hacked on.

jEdit had decent code completion. It actually popped up upon hitting period (which was good), but, strangely enough, only inside of class definitions (not good). I don’t know if that’s a feature or a bug. Stupid either way, though. jEdit’s biggest problem is that it felt like a text editor with an IDE hacked on.

Hurry, Allan!

Technorati Tags: , , ,

Yet Another Ruby/Python Article.

A coworker of mine has been going on about Python for ages. I’ve been quite happy on my little Perl island, not doing much more than writing little scripts for doing short menial tasks or scraping web sites. I thought it was about time to get with the times and update my knowledge of programming languages. I remember stumbling upon Ruby years ago (not quite this early; maybe a year after) and not thinking much about it. Python always seemed so distant, like I could never see myself using it for anything. In Mid-2001, I got into PHP in a big way. All my sites became PHP-based, and I was advocating PHP for any new sites we would build at the Web design company I used to work at. None of the code I wrote in PHP or Perl was really all that OOP, because it never seemed warranted. I’ve known about OOP since I was 16, but I’ve never seen a practical example that showed it’s merits, even through university (when I went through too late to learn C++ and too early to learn Java, so I learned Turing instead). It wasn’t until my latest job, where I got exposed to .Net and C# that I really learned the value and flexibility of OOP. I’ve since taken to it luck a duck to water.

Now I’m trying to find a comfortable language to use for my hobby projects outside of work. Seeing as I’d be doing my development on Mac OS X, Mono would make the most sense, but the maturity level doesn’t seem to be quite there, yet. Java seems to be the next best choice, and I likely will take the time to learn it soon, but it really feels like last decade’s technology (i.e. a little long in the tooth). It’s a mature language/framework, and a first-class citizen in the world of Mac development, but it feels like it’s being leap-frogged by something. Basically, it doesn’t feel all that exciting to learn.

That brings us to Python and Ruby. I don’t know much about either, but what I do know is that I don’t know a little less about Python, because I’ve at least looked at some programs written in Python. From the sounds of it, most people fall into one or the other’s camp, but one thing seems to be clear: either is better than Perl.

I’ve spent the last couple of days checking out Python, checking out Ruby, checking out Django, checking out Rails, checking out TextMate, and checking out Eclipse, and I’ve come to this conclusion: I need to check them out a little longer. Eclipse seems like a really good IDE, but not for me. It doesn’t adhere to the standard keyboard shortcuts for navigating through text as I’ve become accustomed to on the Mac (nor does it seem to adhere to any Windows “standard”). The shortcuts seem fully customizable, which gets you part of the way, but there are other behaviours that don’t seem customizable, and I don’t have the time/patience to babysit my IDE. I need to spend the next little while running TextMate though its paces. Vim is my editor of choice, but definitely doesn’t adhere to OS standards.

Right now I’m leaning towards Ruby. The latest stable version (1.8.2) comes pre-installed in Tiger. I downloaded Rails, installed it, and had the boilerplate page up and running in less than five minutes. There was nothing painful about it. Rails looks good, but what happens when the database you’re trying to build the interface for is not so simple as having primary key columns named ‘id?’ Django looks pretty good, too. I’ll have to check it out when I kick into Python gear.

Technorati Tags: , , , , ,