Why? Well, I’m ready for blogging to be uncool.  I’m ready for something else … like … well, I guess if I knew I would be doing that and not writing a post.  Anyway, what I’m trying to say is that Storples will be on pause until the next cool thing comes along, or I come up with something that becomes cool.

The web is supposed to be fun, and posting blogs so that people I probably talk to everyday can read about something I probably told them at lunch … is not that much fun (to me).  Maybe my audience is too small, or maybe … anyway, you get the point.

I won’t say, come back soon, or any boring stuff like that.  You’ll stumble across here again someday, or I’ll tell you to check it out.  Until then, enjoy!

Nonetheless, I was forced to find an alternative solution.  I turned to Mozilla’s offering, Thunderbird, after having been please so long with Firefox.  However, I was less than thrilled with Thurderbird 2.  Because I don’t plan on talking about Thunderbird 2, I’ll just say that it left me wanting.  And that’s when I found out about Thunderbird 3.

I’ve been using Thunderbird 3 from the earl alpha builds until today (as beta 4 pre, or a nightly beta 3).  Essentially, it’s nearing the end of it’s beta phase, and in perhaps a few short months, it will be ready for public consumption.  Compared to TB (Thunderbird) 2, it feels like a complete redo, and it may very well be.  While it still is not a beautiful to look at as Mail.app, it is certainly within the realm of a good looking app.  But more than that, it just works.  There are points that I wish would be better, namely the way accounts are managed.  But overlooking that, Thunderbird 3 is simply amazing.  I recently discovered that it integrates within Spotlight on OS X, and something Mail.app has had that I did not realize TB 3 has, global searching of messages.  This alone may seem like it should be automatic, but currently it’s an option you have to enable, but once everything is indexed, finding emails across all account is stupid easy.

I recently was an attendee at OSCON and was lucky enough to meet David Ascher, CEO of Mozilla Messaging.  From David’s presentation, I learned quite a bit about TB 3, especially how things on screen are rendered.  To my surprise, I learned it was essentially HTML and a bunch of javascript.  It actually has an internal copy of jQuery, which makes javascript development easy, yet powerful.  I was so impressed by all of this, I have decided to start developing / bug fixing TB 3.  I look forward to helping make TB 3 a better product, so that perhaps others will find it as useful as I have.

Sure, there is a small part of me that hopes Apple gets it right with Mail.app in OS X 10.6, but even if they do, I very likely will stick with Thunderbird … if only due to the simple fact that is is a powerful, easy to use mail client (and is available on Windows too!) that does what it’s supposed to.

With this is mind, I quickly decided that going from 3G to 3GS was simply not worth the money. The iPhone did pretty much all I needed it to do, and anything the 3GS did that the 3G didn’t do, I just didn’t care really. Compass? Who cares. Faster? Probably barely noticeable.

Enter gazelle.com.  Not only did they say they’ll buy my iPhone 3G from me, but they’ll give me more than a new 3GS would cost me (excluding taxes, etc).  But, could they be trusted?  It didn’t take long to find out that they had been well mentioned on such sites as Wired.com, and NYTimes.com … I was sold.  I hoped on over to their site, answer a few questions, and within a few days I had a box to mail them back my 3G for some cash.  How easier could that be?  Back to gazelle.com in a bit.

With my 3G essentially sold, I wasted no time in acquiring a 3GS … and oh boy, was I completely wrong about it being marginally better than the 3G.  First off, it has twice the RAM as the 3G.  That alone makes a huge difference.  On top of that, the CPU is (essentially) 1.5x as fast as the 3G … but it’s not just raw CPU speed, but an updated processor with additional efficiencies that come along with newer processors.  No longer did I need a screen protector, which I only used to reduce finger prints.  The oleophobic (read oil fearing) glass resists finger prints so much, a screen protector just isn’t needed.  As before, the screen is high quality glass, and is scratch resistant on its own.  In addition, the compass actually adds value by being able to determine which direction you’re facing.  On top of all of that, the camera almost alone makes it worth it.  Not only is it now 3MP (up from 2MP), there is now a video recording feature.  With video editing, and ability to upload directly to YouTube via wife or 3G, it’s no wonder that there has been a huge jump in mobile videos being submitted to YouTube.  All around, if you get the full subsidy from AT&T (I know, another 2 year contract, but I happen to like AT&T’s service for the most part) and you can get a good enough deal via gazelle.com (or eBay, etc), I fully support any decision to upgrade to the 3GS.  You will not be disappointed whatsoever.

And how did selling my iPhone 3G to gazelle.com turn out?  Well, as of this writing, I have a check coming my way for > $200, which essentially means I paid nothing to upgrade to the new iPhone 3GS.  You certainly can’t beat that!

So, if you’re interested … check out Microsoft’s website on Friday, or probably 10 dozen other sites who will be following the story.

http://blog.wired.com/gadgets/2009/01/microsoft-relea.html

Enjoy!

In pulling data from a MySQL database for example, one might use the following PHP code:

1
2
3
4
5
6
7

// MySQL database connection code previously defined
$statement = mysql_query("select first_name, last_name from users");
 
while ($user_data = mysql_fetch_assoc($statement))
{
	echo "First Name: " . $user_data['first_name'] . " Last Name: " . $user_data['last_name'] . "\n";   
}

Line 2: this is our MySQL query.
Line 4: our while loop that goes through each row of returned MySQL date. mysql_fetch_assoc puts the MySQL data into an associative array. (see array detail below).
Line 6: here we echo everything out to the browser.

This would obviously pull all the first and last names from a users table, and print them out nice and neatly. Notice that I used $user_data['first_name'] and user_data['first_name'] to pull the first name and last name, respectively. User data is built like so:

Array
(
    [first_name] => John
    [last_name] => Doe
)

So when I code $user_data['first_name'], what I’ll get is “John”.

The same code in Perl might go something like this:

1
2
3
4
5
6
7
8
9

# $dbh, or the MySQL database connection, was defined early in the code
my $statement = "select * from users";
my $sth = $dbh->prepare($statement) or die "can't prepare the statement";
my $rv = $sth->execute or die "can't execute the query: $sth->errstr";
 
while (my $user_data = $sth->fetchrow_hashref())
{
	print "First Name: " . $user_data->{'first_name'} . " Last Name: " . $user_data->{'last_name'} . "\n";   
}

Line 2: our MySQL query.
Line 3: we prepare the statement for execution.
Line 4: we execute the query, calling die if there is an error.
Line 6: similar to the PHP while, we put the MySQL data into a Perl hash, very much like a PHP associative array.
Line 8: here we print it all out.

The output of this code is exactly the same as the PHP code. Sadly, it took me learning PHP to realize that you could even do this with MySQL data, and so … for many years I annoyingly coded my MySQL data in perl using indexes ($user_data[0] instead of $user_data->{‘first_name’}).

Anyway, I hope this helps understand how to make Perl do what PHP does so easily. Enjoy!

In more recent versions, I attempted to bring it up to speed with face lift after face lift, all the while not improving on the one thing it lacked … content.

So here we are today.  I am sadly abandoning the old ways … detailing “what I’ve been up to” or “check out this sweet car”.  No, today I turn Storples into what I have wanted it to be for quite a long time … a technology blog.

I am sure to alienate most, if not all my long time readers … and I’ve come to terms with that.  Hopefully these half-dozen or so people will find it still interesting, but if not, I appreciate the attention you gave the site all these years.  I couldn’t have done, or rather, wouldn’t have done it with out you.  Sure, there will probably never be a GOTW again, but surely you’ve found better places to find that stuff by now!

Anyway, here we go …