My Stuff
My Amps

Add this feed to a running copy of BottomFeeder

Linux World 2006 Speaker

Tuesday, August 30, 2005

Coheed & Cambria

So, I was watching Fuse with my wife the other night and thank goodness for Tivo. I was enthralled by this one commercial with this great music and montage of creepy images. At the end of it all, it showed the roman numerals, "IV" and that's it. We reversed back and got the band name, "Coheed & Cambria". Well, I googled and got to their band page. From there, I listened to some more samples and I was hooked enough to buy one of their CDs. It has to be one of the most incredible pieces of music that I have heard in a long time. It's pure and simple rock with lots of melodies and harmonies. Gorgous does not do it justice. I can't stop listening to it. I've now got all of their CDs on order and I can not wait until their new album, "IV" comes out at the end of September. If you want an idea of what to expect, it's progressive rock without being pretentious and the albums are concepts based around a science fiction story which they have graphic novels for. I'm getting the novels next week. Mark my words, these guys are going to be HUGE. I hope to make a trip to Lawrence, KS in October to see them. I didn't know people still made ROCK records like this anymore. Apparently, they do and there's a whole genre of bands doing stuff like this. Thoughtful, arty music, but with their feet firmly planted in creating memorable hooks. This is what made Black Sabbath, Led Zeppelin, Yes, and Queen great. ROCK ON!


Sunday, August 28, 2005

Too Funny

I see the next shirt that I'm going to have to buy. CLASSIC! The Ruby guys are really giving java a lot of hell. A light-hearted jab in good fun. Ruby on!


Saturday, August 27, 2005

Excited about Squeak 3.9

Traits will come with Squeak 3.9. How awesome is that? Prepare to have another weapon added to your arsenal. Of course, if you can't wait like me, you can download it now in 3.8 via SqueakMap. Squeak on!


VOIVOD Guitarist DENIS 'PIGGY' D'AMOUR Dead Of Colon Cancer

It was reported yesterday that Piggy of Voivod died of cancer at the age of 45. Wow. It took me years to get into Voivod, but once I "got it", they've been one of my faves. Piggy was an incredible and unique guitarist. He will be missed. I got to meet him at Ozzfest a couple of years ago and they were incredibly nice and appreciative. I can't believe another hero is gone. I will be spinning "Dimension Hatross" and "Nothingface" in remembrance. RIP, brother.

  • This saddens me, no end. I used to be pen pals with Denis when I joined their fan club, Iron Gang, around 1983. He was always the one to write back. I finally got to meet him in the 90's and partied with him, Snake, and Away on The Outer Limits tour. Denis was EXTREMELY underated. I can honestly say NO ONE sounded like him! Or Voivod, for that matter!
    RIP, Denis.

    Tim Shockley

    By Anonymous, at 1:01 AM   

Friday, August 26, 2005

The Future and The Ordinary

Suppose you are absolutely certain that a technology that you know about will succeed. How long will it take to have a major impact? Warning: Technologies take a surprisingly long time to become accepted.

The above quote is taken from Donald Norman's "Defending Human Attributes in the Age of the Machine". He gives insight in why new technology takes so long to adopt and even gives some examples of outmoded technology that we still use (the "qwerty" keyboard). Then, he explains several examples of modern technology and how long it took them to be accepted. The numbers are staggering. The television took seventy years from inception to acceptance! He gives a lot more examples and it's quite the read.

Where am I going with this? I think this applies to computer languages and frameworks. The rest of the industry keeps edging toward Smalltalk and Lisp. The road to Smalltalk was started with C++ (by mimicing OO features) gaining acceptance. Later, it was java (VM, garbage collection) and now, python and ruby (late-binding, dynamic typing, closures, etc). Each jump has taken about ten plus years each. What will the next jump be? I'm hoping it will be toward the image because it's the only piece missing. But, we still have about ten years before critical mass. Are you patient? I think I can be.

Each technology jump toward Smalltalk should be celebrated. I tend to be disappointed with each jump because it's not far enough, but I should be happy. Everyone is one step closer to feeling the love. Oh, I can wait ten years for love. Can't you? Now, the question is how long will it be before prototype languages are accepted? I'm betting at least twenty years from now. Well, that's a lot of time to be ahead of the curve and kicking everyone's butt don't you think?

  • Hi Blaine,

    Rumor has it that Ruby will be sporting something like an 'image'... Of course I can't validate the rumor; I received this second-hand information second-handedly ;)

    It really is good to see languages advancing towards Smalltalk. Gives me hope. :)

    By Mel, at 9:23 AM   

  • Moving to an image approach and then improving on that would be goodness.

    Then where do languages go?

    Sooner rather than later they need to embrace concurrency and distribution. Languages need to bust out of the image, even though it makes sense in the small.

    By Patrick Logan, at 11:57 AM   

  • "It's well known that I tried to kill Smalltalk in the later '70s. There were a few years when it was the most wonderful thing in the world. It answered needs in a more compact and beautiful way than anything that had been done before. But time moves on. As we learned more and got more ambitious about what we wanted to do, we realized that there are all kinds of things in Smalltalk that don't scale the way they should - for instance, the reflection stuff that we had in there. It was one of the first languages to really be able to see itself, but now it is known how to do all levels of reflection much better - so we should implement that."
    A Conversation with Alan Kay, Dec/Jan 2004-2005

    By Isaac Gouy, at 1:26 PM   

  • Some celebrate each advance towards a better engine, however, people buy cars.

    Eventually it will be the tools that will sell the language, not the language itself.

    Lots of effort is being poured into tools. If tools and the speed of the hardware can simulate all the goodness of Smalltalk and hide the ugliness for whatever language is under the hood, alas, Smalltalk won't get much traction.

    Intentional Programming and Software Factories just might leapfrog over any "better languages". Most folk like tools, not ever changing, ever improving language syntax... else eMacs would have overcome Windows in the marketplace.

    By Socinian, at 5:34 PM   

  • IBM makes a ton of money on the tools, like WebSphere, not the languages that run on it like HTML or Java, while Sun loses money on the language. Macromedia and Adobe make money on the tools, not the language. Windows & Office are the tools that make money. The API is the language that locks it in, not the programming language.

    Tools are more hardware, network, distribution, concurrency end-user-skill aware than the language.

    At best, Smalltalk should leverage its language advantage to make better app dev tools. Croquet's "shared image" and "massive collaboration" might be the only killer app tools out there.

    The image alone won't do it. Any tool that allows anyone to make true := false and thereby corrupt all data and all code and relies on a questionably timed backup of the entire environment for restore, is suspect.

    By Socinian, at 5:54 PM   

  • 10 or 20 years if you are lucky. We only took 100 years to use the printing press for something other than bibles...

    By Andres, at 11:15 PM   

Thursday, August 25, 2005

Service Provider Went Nuts

If anyone sent me email today and I haven't replied, please resend it. My service provider's email server went nuts and I know I lost some email, but I don't know how much. So, if you don't have a reply from me, I'm not ignoring you. Thanks!


Wednesday, August 24, 2005

Amen, brother

Sam Tesla has a simple prayer that we should all say several times everyday. Right on!


I, Prototype

...unfortunately, Self was not the last object-orientedprogramming language. Self does have some claim to be the lastinteresting object-oriented programming language, or at least the lastinteresting modern OO language with most languages coming afterwards,C++, Java, C#, Cb, being as distinguisable as Coke from Pepsi orMalboro from Rothmans: you dont drink the drink, you drink theadvertising (Twitchell 2000). In Self, at least you can hear yourselfscream.

I must admit that I agree. The above quote is taken from the paper, Attack of The Clones.It's a paper that shows some of the patterns from GoF book implementedin Self. It has to be one of the best reads I've come across. It'scertainly entertaining. Here's some more:
Anotherlovely, natural example of dynamic inheritance in Self. You could dosomething almost as nice Smalltalk using doesNotUnderstand but theSmalltalk Companion doesnt talk about it because, well, theyre wimps(Alpert et al. 1988). You can also do exactly the same thing inSmalltalk using Wrappers (Brant, Foote, Johnson & Roberts 1998).

TheSmalltalk companion is one of my favorite books and I wouldn't callthem "wimps", but it just made me chuckle. And I can't forget this one:
How hardcore do you want to be?
How many lifetimes to you want to waste?

Idon't want to be hardcore and I'm tired of wasting lifetimes...=) Thisarticle is just another one that is making me fall in love with Selfand prototype-based languages more and more. I can't wait to implementand play with these in Io.


Monday, August 22, 2005

Bob Moog Dead at 71

It's sad when your heros start dying. Moog synthesizers are known around the world as being the best. Moog was one the first electronic instruments makers (apparently, he was inspired by what he saw at Raymond Scott's house). He started out making Theremins which are the things responsbile for all of those eerie sounds in 50's horror and sci-fi movies. He's been such a fixture and icon in electronic music. I'm so shocked. I was hoping to meet him one day and thank him for all of the good that he put into the world. Love is lots of knobs and flashing lights to make wonderful sounds. He was the inventor and catalyst for it all. He will be missed. I'm going to go plug my mooger foogers in right now and play in remembrance. Why can't the good ones live forever?


Shameful and Unprofessional

Iron Maiden was pelted with eggs at their last show of Ozzfest. Here's a personal account taken from Blabbermouth:
The manager of a well-known heavy metal band (*NOT* IRON MAIDEN) who attended this past weekend's Ozzfest show at the Hyundai Pavillion in Devore, California has submitted the following first-hand account of the evening that will surely go down as one of the most shameful moments in recent rock history (NOTE: at his request, the author's identity is being protected by BLABBERMOUTH.NET):

"Saturday night's Ozzfest at the Hyundai Pavillion near Los Angeles was a debacle on so many levels, I am still in shock as I write this. As a fan of many of the bands [Saturday] night, one can only hope this was an isolated incident, but sadly, it most likely wasn't. As many of you have heard already, co-headliners and metal legends IRON MAIDEN were pelted with eggs, bottle caps, beer cups, spit on, had people from the Ozzfest camp talking over the PA during their set, had 'Eddie' delayed from his onstage entrance, had members of the [BLACK LABEL SOCIETY] entourage rush the stage with American flags, and had the PA intentionally turned off over 6 times, all by the OSBOURNE CAMP.

"While it's still unclear as to the exact reasons why the terrorizing started (rumors abounded as to why, with everything from Bruce calling out Ozzy in the U.K. rock magazine Kerrang! on the widely known fact that Ozzy uses a teleprompter, to various vague references said on stage about a 'reality show' at an Ozzfest stop in Detroit), one thing was very clear: The whole thing stunk, and left me, and nearly all of the 40,000+ heavy metal fans in attendance angered and disappointed. Not that behind the scenes bickering or magazine trash talking is anything new to rock fans, but the shocking lack of professionalism at one of the largest stops in North America in front of 40,000 + spectators, at the hand of the Osbournes was nothing short of disgusting.

"It all began early in the afternoon, when many side stage bands were openly approached in clear view of everyone backstage by Sharon and Kelly Osbourne to 'join them in throwing eggs at IRON MAIDEN this evening.' All the bands were encouraged to rally the other side stage bands to do so. Members and/or friends of the hardcore band BURY YOUR DEAD were seen actively trying to encourage other side stage bands to 'join in the fun.' Thankfully, many side stage bands angrily declined.

"Later that evening, as IRON MAIDEN came on stage, their intro was interrupted by [BLACK LABEL SOCIETY] hanger-on and biker wannabe Big Dave, who was at the soundboard loudly chanting 'Ozzy, Ozzy' over the PA. MAIDEN opened their set and the entire band was pelted from the front row with eggs, beer, beer cups, spit, and various other objects by an Ozzfest-credentialed, bandana-wearing, Osbourne entourage. IRON MAIDEN, ever the professionals, continued through their set, and by the time they launched into their second song, 'The Trooper', Bruce changed into a civil war-era, red coat and began waving a Union Jack — British flag. Then, someone in, or associated with, BLACK LABEL SOCIETY tried to rush the stage waving and American Flag with the words 'Don't fuck with Ozzy' scrawled across his bare chest. He was tackled and beaten by MAIDEN crew and promptly thrown off stage.

"As 'The Trooper' ended, frontman Bruce Dickinson, with characteristic spunk, launched into a scathing attack on the people terrorizing his band, calling them 'a sorry excuse for an Ozzy Osbourne fan,' and wondering aloud how, 'three dozen eggs could get snuck into the front row of Ozzfest by people with Ozzfest laminates?' Though he never named names, all in attendance could understand who he was referring to. Nicko McBrain ran up to the front asking Bruce to hold on while he cleaned egg off his drums. He then stated the the next song wouldn't be heard on 'Your local cocksucking corporate radio station, wouldn't be seen on MTV anymore, and sure as hell wouldn't be played on a fucking reality TV show,' met by a huge roar from the crowd.

"During the song 'Hallowed Be Thy Name', Bruce, after only the first two lines, stopped singing and ran to the front row, firing back at his terrorizers, saying 'That asswipe right there, with the curly hair, the fucking glasses, and Ozzfest laminate throw his fucking ass out of here right now. It's gonna take more than eggs to stop IRON MAIDEN, and if it wasn't for a lawsuit, I'd rip your fucking head off right now, you piece of shit!!!!' He had the various attackers ejected and continued with a blistering version of the song until right before the big sing long at the end, the PA was INTENTIONALLY cut off. When it came back, Bruce launched into another scathing attack saying that they were supposed to play a shorter set than normal today, and only play 55 minutes, but IRON MAIDEN can't drive 55, or play 55, and were going to play our whole fucking set tonight.

"The band endured six more 'PA cuts,' including having the power to their amps turned off at one point. When the PA would come back on, they would simply launch into the next IRON MAIDEN classic, never missing a beat. Frankly, with every PA cut, the band just got meaner and meaner, playing each new song with an anger and a fire that was at times, simply astonishing to watch. Bruce began the introduction to IRON MAIDEN with a speech about 'Your constitution has something about 'We The People.' Well let me tell you, the only reason we are up here tolerating this bullshit, is because of you people. You have been amazing Glen Helen, and there are A LOT of IRON MAIDEN fans here tonight,' eliciting a huge roar from the crowd. He continued, 'It's gonna take more than eggs to stop IRON MAIDEN, NOTHING is going to come between us and our fans, and it will be death before dishonor, this is 'Iron fucking Maiden',' which was greeted by a thunderous applause. During 'Iron Maiden', longtime MAIDEN mascot Eddie was purposely delayed from making his entrance, making a brief appearance at the end, and one could only wonder as to how. As the band closed there set with a furious version of 'Sanctuary', the PA was again cut only to have Big Dave repeatedly chant 'Ozzy' over the PA, while the band tried to say goodbye to their fans. The now-furious crowd angrily drowned him out with chants of 'MAIDEN, MAIDEN.'

"Then, not 10 seconds after MAIDEN left the stage, Sharon Osbourne walked on stage and predictably, tried to give MAIDEN some fake, half-hearted praise about how they'd like to 'thank IRON MAIDEN,' and what a wonderful band IRON MAIDEN are, and how their crew were 'fantastic,' then sneering, 'But Bruce Dickinson is a prick.' The entire crowd, now fed up with the entire affair, began loudly booing her, pelting her with beer cups, and yelling 'bitch.' She tried to carry on, adding that 'Bruce had disrespected Ozzfest,' only to be drowned out by an ocean of boos, and soaked with beer. She slammed the microphone down and stormed off stage. Many in the crowd, fed up with what they had just witnessed, especially considering that many had come solely for MAIDEN, and paid upwards of $150 to do so, left in droves. SABBATH played to maybe half the audience that was there prior, and seemed stagnate compared to the band preceding them. As a huge fan of SABBATH, I honestly couldn't stand to watch them.

"I've seen IRON MAIDEN probably 10 times in my life, and frankly this was the very best IRON MAIDEN show I've had the pleasure of witnessing. You DON'T want to fuck with IRON MAIDEN. The more the Osbournes tried to fuck with them, the better they got! IRON MAIDEN was on fucking overdrive! Considering the amount of terrorizing and intimidation that IRON MAIDEN had to deal with at the hands of the Osbournes and the other side stage and main stage bands participating, they were the consummate professionals. They had the crowd in the palms of their hands, and IRON MAIDEN and Bruce Dickinson proved beyond a shadow of a doubt why they are the greatest metal band on earth right now, and quite possibly, the classiest, too.

"The Osbournes are drunk with power. Shame on them, and shame on ANY of the bands that participated in the terrorizing and intimidation. It was disgusting display, that NO BAND should have had to endure, but especially a legend like IRON MAIDEN. That fact that it happened in front of 40,000+ people, at a Clear Channel-sponsored event, while Hyundai Pavilion Security turned a blind eye and let the Osbourne camp pelt one of the main headlining bands with eggs, beer, and spit, was simply inexcusable.

"I will proudly be attending next year's MAIDEN fest, and as much as I hate to say it, I can't bring myself to spend another dime on the Osbournes.

"Ozzfest, hang your head in shame."

Indeed...I can't believe this happened. This takes unprofessional to a whole new level. I have new found respect for Maiden for putting up with so much crap. And if it is true that Sharon had anything to do with it, I might have bought my last album of any of the bands involved and seen my last Ozzfest. I can't express how unmetal and deplorable this was. Up the irons.

  • Check out the following:

    What a contrast!

    By Andres, at 10:21 PM   

  • We know that it was a sharon osbourne idea...So she has to leave music business. She destroyed ozzy and sabbath but she cannot do the same thing to iron maiden.
    UP THE IRONS!!!!!!!

    By Anonymous, at 7:33 AM   

Fly On The Wall

I wish I could be a fly on the wall at the Vancouver Lisp User's Group when Avi gives his Seaside talk. I think it would be not only a fun talk, but I would love to hear the resulting conversations. Avi has taken the basic continuation-based web server that started in Lisp and has taken it much further. The suggestions of Lispers would especially be interesting. Makes me wish I lived in Vancouver.


Team Design

I was reading "The Cognitive View: A Different Look at Software Design" by Robert Glass. And the following quote struck a chord with me:
Those same researchers have been looking into team design. And
they’ve found that, in many ways, it’s a shared form of individual
  • The teams create a shared mental model.
  • Team members, sometimes in their own minds and sometimes in the group, run simulations against the shared model.
  • The teams evaluate the simulations and prepare the next level of the model.
But in some ways these efforts are unlike individual design:
  • Conflict is an inevitable part of the design process. It must be managed rather than avoided.
  • Communication techniques become a vital part of the design process.
  • Issues sometimes "fall through the crack" because no individual claims responsibility for them.

I'm always preaching about a "common vision" on the teams that I'm on and I always feel strongly about obtaining it. All of the successful teams that I've been on have had this "common vision". It's a shared goal and reaching for the same target. Without it, every individual has what they think the design should be and you end up with an unmaintainable big ball of mud. It's his first bullet point! A well-oiled agile team achieves all of the first bullet points and knows how to manage the last set. In fact, the last set of bullet points really boils down the problem of unsuccessful teams well. Healthy conflict resolution is paramount to a successful team. Mr. Glass goes on to define what a consider to be the definition of a good IT manager:
In managing design, managers can focus on communication facilitation and conflict resolution as their contribution to design. The empirical studies researchers further suggest that management of design should be the management of the key issues that arise during the design process.

The manager's job should be removing obstacles from the software designers and coders and not standing over you make sure you get your job done. If as a manager, you have an employee that you have to stand over to get their job done, then you've hired the wrong person. You should be making sure your developers have a proper road to race toward the goal on.

There's a lot of nuggets of information contained in and all in all a good read.


Dynamic Languages Help You Design

Darrell Norton makes some interesting observations from "The Cognitive View: A Different Look at Software Design" in his blog entry, Dynamic languages work closer to how you design software. He combines points from this article with the one I mentioned earlier. All three articles are worth a read. I especially love this quote at the end of Darrell's blog entry:
"when I want to focus on the domain problem and not the implementation in curly braces, End If's, or angle brackets, dynamic languages are a (good) answer."


Why REPL is a good thing

Here's a great article on why REPL (read-evaluate-print loop) is a good thing. He mentions using IronPython for .Net, but you can get the same functionality in java with Jess, Groovy, jRuby, and of course, jPython. I love the mentions of Smalltalk. REPL allows you to try out designs and code out quickly. Smalltalk compiles code when you save and you never notice it. One thing that people don't realize is that you are inside a running system that you can change. Any change you make to the system is live, it's not operating on a dead instance of the system. It's the same functionality that gets blank stares at "Ruby On Rails" demos. Sad thing is we've had this for over 20+ years in Smalltalk and Lisp. I'm just glad our industry is finally coming around.


Sunday, August 21, 2005

Cool Pavement Drawings

Juian Beever is a pavement artist that does great work. Check out his website and go down to the 3D illusions gallery. INCREDIBLE! Here's one to whet your appetite:

I would probably walk around that if I saw it! Great optical illusions. MAD FUN!


Saturday, August 20, 2005

Kent Beck vs. Alan Cooper

My friend, Larry Brodahl, sent me a classic article debating Extreme Programming vs. Interaction Design from both of their visionaries. I would love to see more debates like this. I wish they would have continued this discussion. It felt unfinished. It was a great debate! We should always be interested in doing things better. And that is what these types of discussion allow. They make us look at what we are doing and question what is not working.

By the way, if you have never read "The Inmates Are Running The Asylum", you need to now! I can't wait to read "About Face 2.0" now.


Friday, August 19, 2005

Object Inheritance

I've long been a fan of "Streamlined Object Modeling". It's a book I keep coming back to over and over. I was reading it recently and wondered why I never noticed the connection with prototyped delegation and what they call "object inheritance". The book is a collection of domain modeling patterns and several use "object inheritance". One pattern in particular expresses the relationship between an actor and a role. For example, let's look at some java code:
* The common behavior of the actor and the role
public interface PersonProfile {
public String getName();
public void sendEmailTo(EmailAddress another, String message);

* The actor's behavior
public interface Person extends PersonProfile {
public void setName(String aName);
public void setEmail(EmailAddress anAddress);

* The role's behavior
public interface Employee extends PersonProfile {
public BigDecimal getSalary();

The implementation is not important. I wanted to show example interfaces and to show the relationships. The point to object inheritance is that the Employee forwards the calls for PersonProfile on to a Person that it holds on to. This allows you to pass around the role or actor through the same interface. Now, you might be thinking that's a lot of forwarding going on. It is. Now, you could get fancy by using a Proxy and an InvocationHandler. In fact, I do something similiar in Smalltalk when I compile the forwarders on the fly. It's a great modeling technique and is useful in several contexts for expressing clarity in the model. Prototype programming languages make this modeling technique easy to implment (no duplication or coding gymnastics required) by the use of traits. Simply put, traits is a composition technique to combine collections of behavior with data to construct objects. To learn more about traits, read the paper, Organizing without Classes.

The good news is that it's simple to do this technique in Smalltalk by use of the Traits package. Ruby even has it through its Delegate framework. Once you start thinking in Traits, it's hard to go back. Have fun with this new technique and happy coding!

"Streamlined Object Modeling" has the best discussion of modeling and implementing business rules in object-oriented languages that I have ever seen as well. It's a great book all around that balances theory and implementation. It's filled to the brim with great advice that every business modeler should know.


Thursday, August 18, 2005

More Good News

It seems BEA is looking at scripting languages to add to its arsenal of products. It seems dynamic languages are making all kinds of head way in the world. ROCK!


SmallHttpUnitTest Rewrite Update

After finally fixing SmallHttpUnitTest for VisualWorks and having talks with several folks at Smalltalk Solutions, I felt it was time to revamp SmallHttpUnitTest. For one, it was slightly misnamed in that the tests are really end-to-end acceptance tests. I was trying to make the navigation easier through the objects. But, somewhere I made a wrong turn. I started to really look at the Selenium Testing Framework. It runs your tests in the browser via Javascript. Nice. It's simple and it works with a nice a table structure like FIT. You can even command it remotely from another language as well such as Smalltalk, java, Ruby, and more.

Well, it all got me thinking how nice it would be to drive the browser like Selenium does, but with the nice object traversal that I used for SmallHttpUnitTest. You can command Internet Explorer, Firefox, and Opera via Javascript. It's a slightly different idea from Selenium in that the web page that you're loading does not need to have any Javascript loaded. The Javascript works externally via a script that runs the web browser via COM (for Microsoft) and I'm still researching Firefox/Mozilla (but, I know its possible to drive them with Javascript as well). It would seem some Ruby people had the same idea! But, I want to take it further. Javascript makes a lot of things easy since it is so well-integrated into the browser.

The pieces of SmallHttpUnitTest that are in Smalltalk will be re-implemented in Javascript. A lot of the browser handling code is no longer needed! The Smalltalk piece will be an external application that watches what you do as you're traversing your web application and takes notes. Once you've finished navigating, you could update your asserts for each page load and have Smalltalk generate the Javascript for you. I'm doing the proof of concept for Internet Explorer since I am more familiar with the OLE/COM model to drive IE. But, I expect Firefox to be a no brainer. I should only have to replace one object and everything will just work. So, you could have one script that drives both. There's a few more surprises that I want to work out and I will be blogging about them. I have a lot of work ahead of me. This a completely different approach than what I was thinking of doing at Smalltalk Solutions. I've been slow doing the prototype, but I have been a busy boy!

You might be wondering how I got the DOM searching of HttpUnitTest working in Javascript since it uses generators and doesNotUnderstand: a lot. Well, that's a topic for another blog entry. Let's just say that higher order functions are your best friend.

  • Why go down the whole COM route, instead of the in-browser javascript model that selenium uses? We're doing a COM approach in work, and it's nasty. We're looking at selenium with envy.

    By Anonymous, at 10:42 AM   

  • Really COM is a small piece. In fact, it's just the driver to get an instance of IE. I don't plan to use COM for Firefox. It's just for the reference implementation. The interesting bits will be in walking your DOM model and more intention revealing tests. Also, the more fun bit will be generating tests. I want to stick to standard Javascript as much as possible. In fact, I'm hiding all of the COM stuff behind an object and so far, it's very little of the code. I will be using more Javascript in the browser, but it will not be in the page.

    By Blaine, at 6:45 PM   

  • Blaine, you should talk to your friend Mark P. He implemented a COM based HTTP testing framework in VAST. Like you, he simply used the COM interface as a browser driver. It's hidden inside an object and he's talked about plugging it into Firefox.

    By Doug S., at 8:52 AM   

Wednesday, August 17, 2005

Java's Coolness Declining

It seems Apple is dumping java for Cocoa development. I've felt the java coolness factor on the decline for awhile now and scripting languages on the rise with the developer of Rails getting Google hacker of year. I love seeing dynamic languages getting more of the lime light. It's going to be interesting how Python and Ruby will change developer's perspectives. No matter what, it will be a fun ride.



I used to hate Slipknot. I thought they were the worst band. I hated their first two albums, I hated their look, I hated everything about them. So, I'm watching Fuse and they sneak in their latest song, "Before I Forget" and I thought, "Wow, what a great song!" Well, I then notice the masks and think, "There's no way this is Slipknot. This ROCKS!" Well, to make a long story short, I bought the album on a whim expecting it to have that song and maybe two others. Imagine my surprise when I loved every song on this album! The amazing thing is that I hate all their albums still (I tried them again). "Vol. 3" has a great mixture of different songs. It's not all one trick. So, I work my way to "Stone Sour" and I love it too. I'm just shocked how a band can go from awful to awesome in my eyes. I can't stop listening to either "Stone Sour" or "Vol. 3". I hope they keep up the great work! This ain't nu metal anymore.


Touche Pussycat!

I overheard this on the ruby mailing list from Florian Groß:

Eric Mahurin wrote:
The biggest problem I have with being able to add/remove/modify methods of an object (using a meta class or directly in the object's class) is the future of optimization in Ruby. Adding methods may not cause too much of an issue, but modifying them sure could.

"Researchers seeking to improve performance should improve their compilers instead of compromising their languages."
-- An Efficient Implementation of SELF, a Dynamically-Typed Object-Oriented Language Based on Prototypes, July 1989

I love this reply! What a great quote. It ties in nicely with "premature optimization is the root of all evil." Amen, brother! Just remember, people used to think Lisp and Smalltalk were too slow as well. Virtual machines used to be a dirty word. Now, java and c# are two of the most popular corporate languages and they both run off VMs. I love the prototype parts of Ruby. They are especially great for debugging specific instances and other things. Let's make our languages more dynamic, not less. More is less.

  • That's a great quote. Ruby could improve a lot though. The first thing I would love to see is Ruby being self-hosted, that way we could have access to the parser and to the compiler directly from withing Ruby. I think that Factor can do it.

    By Vincent Foley, at 10:09 PM   

  • Hehe, like I said -- there couldn't possibly have been a better opportunity to post that with SELF being a prototype based language and all that. :)

    By Florian Groß, at 5:15 PM   

Sunday, August 14, 2005


I just found this document on the net entitled "How To Become A Hacker" By Eric Raymond. I read through a bit of it and I couldn't believe it. I stopped reading it immediately. Am I the only programmer offended by crap like this? I hate the words "geek" and "nerd". And "hacker" to me means someone who programs Big Balls Of Mud and doesn't care. This kind of junk just keeps stereotypes of smart people alive. It's derogatory and offensive. It's like the stereotypes of southern people. We don't all live in trailer parks and listen to country music. It's just like not all smart people are social misfits, play dungeons and dragons, and can't wash ourselves properly. I'm tired of the demonizing of intelligent people. We are the problem solvers of the world and you'd think that would be respected and revered. You'd think we wouldn't perpetuate bull crap like this. OK, ok, I'll get off my soapbox.

  • Blaine, what happened?

    I'm not used to this kind of comments coming from you. I call myself a hacker and I didn't see anything offensive.

    Am I the only programmer offended by crap like this? I hate the words "geek" and "nerd". And "hacker" to me means someone who programs Big Balls Of Mud and doesn't care.

    I guess that sums it up, you seem prejudiced by some words so you refused to read the actual information. If you read a bit larger part of the doc you'll see that it doesn't line up with 'not caring' about big balls of mud hackers create.

    Wish you a better mood ;-)

    By Reinout Heeck, at 4:10 AM   

  • Dude, calm down. Have some dip.

    I used to be offended by "geek" and "nerd" but in the last 10 years there has been an effort to reclaim the words as our own. It's something like whats happening to the words "gay", "queer", "fag", etc. in the gay community. You take the word and use it in a positive manner to change it's meaning and wrest control of it from thoses who would use it in a derogatory manner.

    Some pretty good definitions of the term "Hacker" are below...The standard community usage is much more positive than you make it out to be.

    By John Dougan, at 4:35 AM   

  • First off, I know my comments were harsh, probably too harsh. It's what I was feeling at the moment. I just needed to vent. I know the historical usage of "hacker" is very positive. But, after hearing so many people use it to mean "bad programmer" it got programmed into me wrong. I'm still working through that because a lot of my heros use it to describe themselves. Maybe one day, I'll come out and proclaim myself a "hacker". One never knows.

    I was mainly offended on a big "how to become a programmer" type of document. To me, all you need is a "how to program" and a thirst for how to make computers do your bidding. The rest will come naturally. Describing how to be become accepted in the community by reading science fiction (one example from the "Points For Style") was just silly. I did like the section: "The Hacker Attitude". I guess the document came off to me like a "dummies" book. Hence, my "rant".

    Now, on to "nerd" and "geek", the way I feel about them is that they are mean words. Something I would never call a friend. I just don't like mean words.

    I'm in a better mood now. But, I've seen stuff lately on "how to date geeks", "how to talk to a nerd", and etc. And I guess the last straw was the "how to become a geek".

    I really do need to get over my definition of "hacker" though. I'll work on that one...=)

    By Blaine, at 7:33 AM   

Saturday, August 13, 2005

I Couldn't Have Said It Better

Hwee Boon Yar states, "Smalltalk just fulfills most of my needs more easily." I couldn't have it said it better myself. Despite some of my blog entries, I don't totally hate java. I'm still looking for the perfect language. I'm just amazed in terms of productivity that nothing has yet to surpass Smalltalk that I can find. Of course, that's not to say that Smalltalk doesn't have some warts, but they don't get in my way.


Friday, August 12, 2005

Thinking Forth

It seems Vincent Foley has been hooked by Leo Brodie's "Thinking Forth" as well. I blogged about it a while back. It's an excellent read. If you don't care for Forth, you still need to read the chapters: Preliminary Design/Decomposition, Detailed Design/Problem Solving, Factoring, and Minimizing Control Structures. It's full of great advice and remember it was written in 1984. Another depressing example of how our industry forgets past lessons. But, I think this trend is changing. Many of us are exploring the past and uncovering lost gems. We shall not make the same mistakes again.


Thursday, August 11, 2005

Smalltalk Shop

Alright, who didn't tell me about the Smalltalk Shop? They have the classic balloon in a poster and t-shirts with that hot new balloon logo. You can even get the logos in different colors! I think I might be buying some stuff soon...=)

  • I was going to send out more announcements once I put up some more things that are in the pipeline, but kudos to anyone who already found it :)

    I will be publishing a few more products within a "Quotes" line, look for pro-Smalltalk quotes from Alan Kay starting Monday.

    By Boris Popov, at 12:24 PM   

  • COOL! I made my order today. I'll be buying more....=) Smalltalk on!

    By Blaine, at 9:31 PM   

Sunday, August 07, 2005


Well, with all of the noise generated by generics in the java world, it seems annotations got lost in the cracks. They allow you to add metadata to fields, methods, and types. With this metadata, you can reflect at compile-time or run-time. This opens a lot of cool possibilities in java! So, I got down and started to write some example code. One of the first snags that I ran into is that they can not be subtyped even though the syntax for creating them is similiar to interfaces. The second snag was adding behavior which didn't suprise me, but I wished for it. Annotations allow you to capture data into structures. But, the more you play with them, the more you desire to use polymorphism instead of using instanceof everywhere. I think it would have made annotations way more powerful and cool. It just seems they went half way. Why didn't they just make annotations full objects? Anyway, they are still a welcome addition to the language and they are the reason that EJB 3.0 is a lot simpler to create entities. Anything that makes java/j2ee simpler is alright by me.



I've been reading up on java 5.0 and I came across this tutorial on the new generics framework.
A note on naming conventions. We recommend that you use pithy (single character
if possible) yet evocative names for formal type parameters.

Huh? I couldn't believe my eyes and what I was reading. But, here's the code sample:
public interface List<E> {
void add(E x);
Iterator<E> iterator();
public interface Iterator<E> {
E next();
boolean hasNext();

I can see why so many java advocates have been clamoring about the complexity. Shouldn't we be making the code more readable? The paper goes through the problems with generics and addresses each one. It leaves you asking yourself, "Is this going too far?" It especially gets messy around how to treat subclasses and interfaces. The answer makes everything more restrictive which sounds good on paper (if you like type safety), but it also reduces polymorphic possibilities. I shutter at the thought of the code that I will come across from inexperienced OO developers. Much like I have seen "private" misused in method declarations. I expect to see generics misused to be more restrictive that they need to be as well. I applaud the effort to reduce the need to type cast, but what price shall we pay for safety? Generics do make like easier for some issues, but it complicates others. Is it really worth it? I find unit tests a much better tool to fix type issues than enforcing type safety.

  • "Shouldn't we be making the code more readable?"
    I'd be interested in seeing your idea of a more readable alternative for those interface definitions - particularly a more readable alternative for 'E'

    By Isaac Gouy, at 2:08 PM   

  • This is why I don't particularly care for generics/templates. It's a tradeoff in readability for something that dyamic languages get for free.

    As far as a better name for 'E', Mr. Gouy, we've been doing this for a long time in dynamic languages (reflecting and passing class references around). I'd be inclined to call it 'ElementClass' or 'ElementType' if you want to convey that you can use it with primitives. The whole idea is that you'll type it once but read it a thousand times, so make it express something.

    By Samuel Tesla, at 4:17 PM   

  • Samuel, I feel it would be unfair to respond to your comments, as Blaine has failed to reproduce the example correctly.

    (Here's the example using square-brackets instead of angle-brackets)

    public interface List[E] {
    void add(E x);
    Iterator[E] iterator();

    public interface Iterator[E] {
    E next();
    boolean hasNext();

    By Isaac Gouy, at 4:57 PM   

  • The point of Blaine's post was that it was unusual, and contrary to accepted naming practices, to name a variable with a single letter.

    The fact that Sun recommends it is astonishing.

    The fact that Blaine omitted some syntax elements is completely irrelevant to his argument.


    By Ravi Venkataraman, at 8:17 PM   

  • Ravi, the quotation specifically states formal type parameters it doesn't say "name a variable with a single letter".

    By Isaac Gouy, at 9:24 PM   

  • we've been doing this for a long time in dynamic languages
    We might have been "reflecting and passing class references around" but we sure haven't been naming formal type parameters.

    By Isaac Gouy, at 11:31 AM   

  • Huh? I couldn't believe my eyes and what I was reading
    I have much the same reaction when I find that the sentence following the one Blaine quotes gives the rationale for the naming convention.

    "making it easy to distinguish formal type parameters from ordinary classes and interfaces"

    iow everyone knows better than to use single letter names for classes and interfaces - so when we see a single letter name, we can be confident the parameter is not a class or an interface but is a formal type parameter.

    By Isaac Gouy, at 11:44 AM   

  • I started to write a response here, and realized that it was big enough to be a post of its own. It's over here on my blog.

    As far as reflection and class references. Yes, exactly. That's my point. We Don't Have To Do This Crap. In dynamic languages we can get all of the benefits that generics bring to statically typed languages without all of the nasty readability problems. Not to mention the complexity bloat.

    Static typing is a language designer's way of saying he thinks programmers are too stupid to write software and that he must make the computer catch their mistakes. Generics are static typing's way of approximating the things that dynamic languages can do because dynamic languages trust the programmer to be smart.

    By Samuel Tesla, at 11:25 PM   

  • Samuel: no secret that the next version of Java will have generics
    Ummm hasn't Java had generics for almost a year?

    Matrix[E, F]
    Of course sometimes we deal with hypercubes made up of strings and doubles and dates and... If we're just doing matrix math, wouldn't all the elements be the same type, irrespective of the number of dimensions? Matrix[T]

    It's funny how often we complain about the rhetoric thrown against Smalltalk by people who've never used the language, but then we don't seem at all inhibited in lambasting something we haven't used ;-)

    By Isaac Gouy, at 2:35 AM   

  • sexual

    By Anonymous, at 2:07 AM   

  • sexual

    By Anonymous, at 2:07 AM   

Omaha Smalltalkers

Well, it seems attendance was light last week and I was hoping that Gary Overgard could give his talk again on doing a report/code distribution on Small-Fit. It provides a lite-weight alternative to the current approach for Fit & Fitnesse. Its advantage is that it is much easier to debug, but still gives advantage of documentation. If we have time, I will be showing Ruby for Smalltalkers talk.

As always bring your passion, code snippets, and books to discuss!

Here's all of the details:

When: August 9, 2005, 7pm - 9pm
Where: Offices of Northern Natural Gas
1111 S 103rd Street
Omaha Nebraska 68154

Office is at 103rd & Pacific. Guests can park in the Northern visitors parking area back of building, or across the street at the mall. Enter in front door, we'll greet you at the door at 7:00pm. If you arrive a bit later, just tell the guard at the reception desk you're here for the Smalltalk user meeting in the 1st floor training room.


Songs That Give Strength

I love music. I love all kinds. But, every once in a while, you get find something special. Something that touches your soul and you completely relate to. There's only a few albums that touch me deeply. But, one artist, Assemblage 23, continues to always write lyrics that dig deep inside of me. I've been listening to his music all week. His lyrics are all introspective and he writes the perfect music to back it up. It's a source of inspiration and strength for me. One song that really gets me everytime I hear it is "Lullaby". Here's the lyrics:

May you find solace in the gentle arms of sleep
Despite the wolves outside your door
In time you will see them all as harmless
And their idle threats easy to ignore

And if ever fate should choose to smite you
Stand your ground, never walk away
Please don't ever let the world defeat you
Don't get buried in its decay

As you drift into the gauzy realm of dreams
May you take comfort in the thought that you are safe
For it only takes a fraction of a second
For all of this to change

Return to me
When slumber's fog has lifted
Return to me
Stronger than before

As you sink beneath the soothing streams of time
May you be thankful that you had another day
For there comes a time when each of us will enter
A sleep from which we will never wake

And if ever fate should choose to smite you
Stand your ground, never walk away
Please don't ever let the world defeat you
Don't get buried in its decay

Close your eyes now, if only for a moment
For it's time you get some rest
The wolves are gone and nothing here can harm you
Let go of your fragile consciousness

His lyrics are about the dark places all of us find ourselves in from time to time. But, there's always this ray of sunshine rising out of the bleakness to get out and make your life better. I love it. I wish I could find more music like this. One of his main influences is Depeche Mode and I've been slowly getting their back catalogue. All great stuff!


One Size Fits All

There has been discussion on the Squeak mailing list about Smalltalk vs. Ruby. It started out as a Rails vs. Seaside question and then turned broader. Personally, I think there is no comparison between Rails and Seaside. Rails includes a simple way to map objects to an OO relational database with a traditional request/response model. Seaside on the other hand does not have a persistence model (they let you decide) and has a more advant-garde yet easier flow model. They both share the simpler is better principle of design, but they have attacked it at different angles. Rails is easier to swallow for most programmers, since it is closer to what they are used to. But, I find Seaside to be the simplest way to build web applications. There are things to learn from both.

On to the broader question of Ruby vs. Smalltalk, there was a lot of discussion of image-based vs. file-based environments. But, I think the one we need to keep in mind is the following quote from Enrico Schwass:
I guess smalltalk and especially squeak get now the chance to spread
wider. Why? Because of the growing ruby community. Smalltalk is
mentioned everywhere. Most of the newer ruby guys are curious enough to
take a look. Like me. This could start a smalltalk renaissance. If you
welcome them friendly :)

The key point is that we should understand that programmers are coming from other backgrounds. We should show them what Smalltalk has to offer and not why we think their language is inferior. We all have things to learn from one another. We need to embrace them with open arms. Smalltalk is cool because it is image-based, but it's a hard sell to a lot of programmers. It presents an alien world that is both strange and unfamiliar. Ruby allows most programmers to stay comfortable in their file-based world, yet take a peak into a pure OO world. One step at a time, I think Ruby prepares programmers for an image-based world. Also, I think they will come to Smalltalk with a different mindset and this will push boundaries. This is a good thing. I am continually amazed at how inventive and creative members of the Ruby comunity truly are. They will be a welcome addition to our community. Besides, who says one language has to rule them all? Let's embrace Ruby for what it's good for and do the same for Smalltalk. I enjoy programming in both and love being a part of their communities. Of course, I enjoy programming in a lot of different languages. Each one has it's pluses and minuses. So, instead of bickering about which one is better, let's learn what's great about each one.

  • Hi Blaine,

    first, I agree with you that Seaside is simpler to use than Rails, it works just like a normal application. I do think however that an ActiveRecord-like package to make database-backed website easier would boost Seaside's popularity tremendously.

    And I agree with you, the Smalltalk (and also the Ruby) community should be open, friendly, non-snob. People should see more than the language, they should see that it's a great place to get help, meet new people, etc. I do think that the image-source file has tremendous advantages over plain text files, however we need to be able to effectivly, but calmly, demonstrate those advantages; nobody likes someone soving concept down his throat, once you discover something for yourself, you're much more likely to enjoy it than if someone called you a fool on the net for having a different opinion.

    By Vincent Foley, at 4:38 PM   

  • I think Squeak in general would benefit with better persistence options for legacy systems. I think this in turn would help Seaside. I like the fact that Seaside is a web framework and nothing more. It allows me to pick the persistence mechanism that works for me.

    As for the communities, I agree 100%. I think people need to remember that. Snobbery hurt the Lisp community for years. Hell, I didn't mess with PLT Scheme for a long time because of their poor behavior at the Lightweight Languages Conference 2.

    Just because someone doesn't your light instantly doesn't make them an idiot. They might have good reasons, listen to them and grow.

    Let's all embrace solving complex problems through simplicity.

    And let's remember the java community is not evil. Hell, I'm apart of that community too. Lots of old Smalltalkers and aspiring full-time Rubyists are there as well. We just all can't wait to do our jobs better.

    By Blaine, at 5:04 PM   

  • Hear here!

    I couldn't agree with this sentiment more. There are so many things that we can learn from the plethora of languages out there. It is part of why I try to learn at least one new language every year.

    Ruby and Smalltalk both have their appeals, and so do Lisp, Objective C, Java, C#, and Delphi (the languages I typically work in). The trick is just to figure out which tasks each language will make easiest and fun.

    By Samuel Tesla, at 9:17 PM   

  • sensual

    By Anonymous, at 4:19 AM   

  • sensual

    By Anonymous, at 4:19 AM   

Saturday, August 06, 2005

10 Things Every Java Programmer Should Know About Ruby

The slides for Jim Weirich's "10 Things Every Java Programmer Should Know About Ruby" are up and ready for your reading. The slides are excellent and provide a great argument for dynamic languages. Everything he talks about is true for Smalltalk as well except that everything really is an object (including blocks) in Smalltalk. I do love Ruby, I think it has a lot of good ideas (like mix-ins). I especially love the Ruby community. It's young, vibrant and they embrace the simple for doing complex things. It's possible.


Wednesday, August 03, 2005

Just Say No....To Kitten Huffing?

My gut is hurting. But, did you know kitten huffing was bad for your health? This is some pretty dark and funny stuff! The included video is simply hilarious. Enjoy.


Tuesday, August 02, 2005

Alice Cooper

The master released his new album, "Dirty Diamonds" and it is brilliant. I'm a huge of Alice and he never has disappointed me. But, I wasn't expecting this. It's a complete throwback to his early 70's material. It's diverse and his twisted sense of humour comes shining through. I can't wait to see the tour! I hope he never stops making albums.


Which Altar Do You Want To Worship At?

"Finally, the days where a novice programmer can know all of a language are gone, at least for the languages in widespread industrial use. Few people know "all of C" or "all of Java" either and none of those are novices. It follows that nobody should have to apologize for the fact that novices do not know all of C++. What you must do - in any language - is to pick a subset, get working writing code, and gradually learn more of the language, its libraries, and its tools."
-Bjarne Stroustrup from What is C++ So Big?"

"If a system is to serve the creative spirit, it must be entirely comprehensible to a single individual."
-Dan Ingalls from Design Principles Behind Smalltalk

Rock on dynamic brothers. Rock on!

  • Ruby! Ruby! Ruby!

    By Vincent Foley, at 9:15 PM   

  • This post has been removed by the author.

    By Isaac Gouy, at 2:45 AM   

  • Preceding those comments, in the same section, Stroustrup writes:

    The programming world is far more complex today than it was 30 years ago, and modern programming languages reflect that.

    The Dan Ingalls quote is 25 years old.

    By Isaac Gouy, at 6:54 PM   

Great Comeback

Doug Stewart sent me an exhcange between Andrew Tanenbaum and Linus Torvalds. What I love about it is Andrew sends a hateful email to Linus. The comeback that he returns is just classic. Here's Alan's email to Linus:
" I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error. Be thankful you are not my
student. You would not get a high grade for such a design :-)"

And here's Linus' answer (Please, put down the Coke can unless you want it on the monitor or up your nose):
" Your job is being a professor and researcher: That's one hell of a good excuse for some of the brain-damages of minix."

The only thing I can say is "Touché Pussycat!"


Wheel Of Fortune Programming

Memory used to be expensive, so developers thought of creative ways to get the most out of the least. One of the ingenius ways to save memory was to abbreviate variable names. What amazes me is that this school of thought has carried on even today. We no longer have memory constraints and in fact, source code is miniscule in comparison to everything else on your computer. Your code will be read more times than what it takes you to write it. More time will be spent understanding it. So, why raise the cognitive friction by playing "Wheel Of Fortune"? Vowels are not expensive. They are free! Remember that the next time you want to abbreviate variables that you are going to make someone do mental gymnastics just to grok something as simple as a variable name. Wouldn't you want them to comprehend the logic instead? Think about it. Where do you want the brain power to go to? Or maybe you like your fellow developers cursing your name at 3:00am when they're trying to fix your code. Have pity for the ones that will read your code. Make it read as closely to human language as you possibly can. It's just good style and polite.


Metalheads Against Racism

This page is powered by Blogger. Isn't yours?