Smalltalk Tidbits, Industry Rants

Recently, I've been reading a fascinating little book: "Spice: The History of a Temptation". It's not a history of the spice trade, or of the Western conquests in that part of the world; rather, it's a social history of spices in the West. The book jumps around a lot, with the chapters split up by topic rather than by time. So we trace through the interest in spices for burial rites, for perfumes, and, of course, for food. There's a lot about the interesting duality of spices in religion - used for ceremonies, but also decried as sinful (not just a Christian worry, apparently - there's plenty of "down the nose" condescension from the Roman era). It's a very interesting book, with lots of interesting snippets. One section that dealt with drinking habits in medieval Europe was interesting - spiced wines arose mostly as a way to make wine last longer, in the era before good sealing methods. Mulled wine - a modern holiday tradition (my wife makes a very nice one... mmm ) - has its origins in the attempts of nobles and merchants to make their wine palatable. One quote I really liked from that section was a description of the average wine as "the wine of astonishment". All in all, it's a nice little read. Highly recommended.

Ok, which new book is this a one line review of:

"I'm going to find whoever told me that geekdom was a celibate profession and make them eat this book!"

Ken Arnold, coauthor of "The Java Programming Language"

If you give up, follow this link :)

Wilkes Joiner demonstrates how to do live debugging in Seaside:

I've created a short (3min) video showing how you can deal with a stack trace while developing a Seaside application. One thing to note is that most of this power and flexibility comes from the Smalltalk environment itself.

As Wilkes notes, this isn't a Seaside specific piece of power - you can do the same thing in any application, due to the power of the Smalltalk system. The server running this blog is typically updated by just filing in patch code rather than the more common (over in the mainstream software world) kill/load new code/restart paradigm.

Time for my weekly perusal of the logs. BottomFeeder downloads dipped to 290 per day last week - the details:

Platform	BottomFeeder Downloads
HPUX	485
Windows	425
Mac 8/9	288
Update	237
Sources	226
Linux x86	125
Mac X	102
CE ARM	63
Solaris	20
Windows98/ME	19
Linux Sparc	15
Linux PPC	10
AIX	8
SGI	6
ADUX	3
Source Script	2

The distribution looks about the same as usual. On to the HTML page accesses:

Tool	Percentage of Accesses
Mozilla	52.9%
Internet Explorer	28%
Other	8.9%
MSN Bot	6.1%
Google Bot	3.1%
BottomFeeder	1%

The volatility in the Mozilla/IE numbers over time is really strange. I have no idea what it means :). On to the RSS numbers:

Tool	Percentage of Accesses
Mozilla	23%
BottomFeeder	18%
Net News Wire	10.5%
Other	9.6%
BlogLines	8.1%
Safari RSS	5.1%
Internet Explorer	5%
Planet Smalltalk	4.6%
SharpReader	2.4%
Magpie	2%
RSS Bandit	1.9%
NewsGator	1.5%
Liferea	1.2%
Feed Reader	1.1%
BlogSearch	1%
MSN Bot	1%
JetBrains	1%
Feed Demon	1%
News Fire	1%
Google Bot	1%

Still quite a large showing for the Mac tools there. Otherwise, still a very diverse set of tools being used.

It looks like the download page lists some confusing information - the references are all to the summer (VW 7.3.1 and OST 7.0.1) release. In fact, the latest release is available, we just didn't get those pages updated. I'm having the text changed over to be more generic - i.e., something like "Get the Latest Non-Commercial Release" instead of a version specific reference. In the meantime, just follow on through and get the latest.

Via Post Prandial:

A century and a half from now, there will be no-one who remembers first-hand what you were like. You will exist to your family (who will be large and many branched by then) as faint traces from the past, appearing only randomly in whatever mementoes sheer luck and institutional planning have created. While scientists continue to work on understanding probabilities of disease and predilections in our double helices, a simple name is the visible DNA that anyone can trace and interpret. A family name is the marker. The context in which it appears is the story it tells us.

Read the whole thing, and you'll get an appreciation for just how transient our appearance on the globe really is. The now seems really important to us, but it seemed equally so to our forebearers - and most of them left very hazy footprints. I have some second hand (via my mother) recollections of her father, and I remember both of my grandmothers - but beyond that - it's all mist.

First, there was the car. Then tonight we got home and found that the milk carton had been leaking into the meat and vegetable drawers. Oh boy - complete mess. On top of that, the upper shelf in our fridge has been half broken for quite some time, and it's only been the utterly inscrutable Sears website that's prevented me from buying a replacement part.

Well, taking the shelf out to clean it completed the break, so I guess I have to deal with that now. Then, to make matters more enjoyable, there was all the gunk that had built up in the fridge. You know - the stuff behind the shelves and under the drawers that you say you'll get to "someday"? Well, with the shelves and drawers out, that day was today. I don't even know what some of it was, which only makes it worse. Gah!

Daniel Poon has joined the Cincom Smalltalk blog community - here's his feed. If the intersection of automotive design and software interest you, subscribe here. I blogged Dan's talk at StS 2006 here.

Last night, Michael and I were playing a network civ 4 game. He crushed me the time before, nuking most of my cities. This time, we were playing on an island board, and I got set up right next to two AI players. No more mister nice guy; I built an army and killed them. Just as I took the second one out, bam - crash.

Michael's crashed as well, so we went to the latest backup and started in - and boom, immediate crash. Clearly, the gods of Civ 4 were not going to be with me :/

Jon Fine has come up with a really stupid idea - he thinks that making content invisible will somehow make it more relevant:

What if 2006 is the year big media players take aim at Google's kneecaps? No, not with more lawsuits; the Authors Guild, the Association of American Publishers -- on behalf, in part, of BusinessWeek's parent company, The McGraw-Hill Companies -- and Agence France-Presse have already sued the search behemoth. Rather, picture this: Walt Disney, News Corp., NBC Universal, and The New York Times, in an odd tableau of unity, join together and say: "We are the founding members of the Content Consortium. Next month we launch our free, searchable Web site, which no outside search engines can access." (A simple bit of code is all it takes to bar all or some major search engines from accessing a site.) "From now on we'll make our stuff available and sell ads around it and the searches for it, but only on our terms. Who else wants to join us? Membership's free."

Yeah, that's worked so well for the Times. Hey Jon - noticed a distinct decline in links over to TimesSelect recently? How do you suppose that happened? You think that making their opinion pieces invisible might have had something to do with it?

Yes, I know that this proposal doesn't involve a pay-wall. It does something just as stupid though - server side directives to stop bots from Google (and Yahoo, and MSN, etc., etc.) from slurping up the links. That's every bit as stupid. I'm using Firefox, and what do you think is right up in the top right corner? Why, it's a Google search box. How do you think I typically search? What do you think MS will ship with the next rev of IE - same kind of thing, only the default will likely be an MSN search. Which is how most IE users will search as well.

Jeff Jarvis nailed this in his riposte:

Well, that would be hugely stupid. And though huge companies can be stupid, I don’t think they’d be that self-destructive. For the truth of life today — like it or not, lump it or not — is that Google is everyone’s front page. And, yes, that can make life difficult. Google kills brands; Google commodifies everything. But that’s not Google’s fault. That comes part-and-parcel with this new, distributed world where we control the entry to the content we want and where there is no longer a scarcity of content that lets a few big players control it and us. Wishing this weren’t so won’t make it not so.

So let me think - Fine thinks that a bunch of content companies should team up, gather their content, hide it from search engines, and then get people to visit. Exactly how would users find the content, since the plan would be to hide it from search engines? I've seen a lot of stupid plans before, but this one ranks up there with the *cough* plot *cough* of "Surface".

This came in from the ESUG mailing list:

We have a (research) position to fill that relates closely with a Smalltalk framework for synthesis and modeling for system-on-chips and reconfigurable circuits.

If you are interested the call is here(PDF)

I see Sun's decided that they don't have enough problems - now they plan to offer an open source DRM solution. I think this quote from their lead on the project, Glenn Edens, says it all:

But Edens isn’t so pessimistic about DReaM. He maintains that while DRM isn’t perfectly secure, it can still work, as long as it doesn’t force users to circumvent it in order to use the product normally. “We’ve started a very fruitful dialog with the EFF [Electronic Frontier Foundation]. We have been working on a white paper to describe a possible solution to the fair-use issues. The hard question is: ‘How can you have an access and authentication system that also respects fair use?’”

The problem is right there in the premise - that DRM can work so long as users can use a product normally. For a music CD, that means making as many copies for personal use as I want, and playing the music in any format I want. In other words, so long as I don't start giving (or worse, selling) the product to others, how I make use of it shouldn't matter. That runs smack into the DRM wall, as it's highly concerned with those exact issues - how many copies (and what sorts of copies) I make.

At the end of the day, the pig is still a pig, regardless of how nice the dress is.

Charles Cook relays a quote from Richard Grimes about .NET usage in Vista:

Finally, there is the issue of WinFX. Initially, this was called the Longhorn API (LAPI) and it was intended to be the foundation of all the applications in Longhorn. Microsoft have retreated significantly from this position. WinFX was not provided as part of any of the builds of Vista, so the clear implication is that Microsoft intends to develop Vista with native code (and possibly with a little bit of .NET through the framework library) and not to use WinFX at all. I cannot stress how significant this retreat is. Microsoft have so little confidence in their own application framework that they will not use it even in their own managed applications.

This is starting to look like a PR issue for Microsoft. I emphasize PR, because I don't think it's really a technical one (beyond the fact that no one thought to synchronize the development cycles for .NET and Vista - and that falls into management).

As Dan Fernandez has posted, there's plenty of .NET usage by Microsoft - the problem is that earlier statements by them on the subject don't make it seem that way. This is why you have to be very, very careful in what you say about upcoming releases and what will be in them. I've made that mistake myself, and I keep it in mind as we promote each of our Cincom Smalltalk releases.

Via Rob Fahrni, I see that Carson Palmer's injury is much worse than what was initially reported:

"Carson Palmer's knee injury was 'devastating and potentially career-ending,' involving numerous ligament tears, a shredded ligament, damaged cartilage and a dislocated kneecap, his surgeon said Thursday."

That sounds like a life impacting injury - never mind football. It didn't look like that big a hit at the time, but it goes to show - anything can happen when bodies collide. I think the Bengals need to look at whether or not Kitna is who they want to go with next year.

Dana VanDen Heuvel reports that CMO Magazine is going dark:

The extraordinary feedback and support from the CMO community has not been enough to sustain and grow our advertising-supported business in what has become a severely challenged publishing environment.

More to the point, they have blogs and are not just old-school publishing folk. These guys really made a run at this.

Is there just not enough of a market for marketing to marketers???

I've been getting CMO for awhile now, and liked it well enough. I think the key issue is that their model assumed that they could get enough advertising support - I was never asked to pay for a subscription. Would I have? I don't know, but they never even asked. Perhaps they should have tried asking for revenue from their readers?

Even the high and mighty get whacked by this stuff:

Now it seems that Steven Spielberg's latest movie, Munich, might miss the opportunity to be nominated for the BAFTA Awards because of some splendidly stupid actions from the publisher. The movies where sent, to the BAFTA members for viewing, as encrypted DVD:s. Not only did the DVD:s get held-up in UK Customs, but when they finally arrived they only worked on a specific brand of DVD Player, Cinea, and where mastered as Region 1 (which is North America) which is pretty useless under normal circumstances in Europe.

The comments from one of the reviewers says it all:

Regarding the special encrypted Cinea player that we were all sent, I never hooked it up and I wonder how many people did. About half of the screeners I received are encrypted for Cinea and the other half weren't. I don't have time to watch ALL the screeners I get anyway so naturally I just end up watching the ones that are easy to watch, that I can watch on my laptop or at a friend's house. I have to believe that those movies that were sent out in the encrypted format were viewed FAR less than those that won't.

When you make the content a pain in the butt to get at, fewer people will look at - even if it's free.

Now that Smalltalk Solutions is co-located with LinuxWorld/NetworkWorld, you'll need to register earlier than you're used to - it's a big show in its own right, and the Blue Jays are in town when the show is being held. Make sure you book early - there are a lot of people attending this show. If the baseball schedule interests you, here's who Toronto is playing at that time:

April 18 and 19 … New York (before the conference)

April 21-23 … Boston

April 25-27 … Baltimore

So register now, and make sure to arrange your hotel!

Update: Apparently, registration isn't actually online yet - I was told it would be today. I'll update this post, and possibly push a new post, when that changes.

I see that Scott McNealy is predicting the demise of the iPod:

Sun Microsystems Chief Executive Scott McNealy consistently credits Apple Computer for good marketing--to the point where he listed what he believes will be his own company's glorious iPod moments. But McNealy said Wednesday believes the iPod itself will be replaced in coming years by music stored in the network.

Yeah, I'm sure that Apple will go into hibernation and pay no attention to ongoing trends. Meanwhile, how's that "everything is free" working out for the profit margins?

I was on my way out to add more memory to my Mini when disaster struck - car made a weird noise and then died. One tow from AAA later, and my mechanic informed me that the car's engine was a goner. Not so bad, all things considered - we got over 130,000 miles out of it.

Here's the thing though - I'm probably just going to have a rebuilt engine dropped in. Why? Because that's going to be about $1000, parts and labor. A new car would run me $300 - $500 a month in payments, so I figure, given my driving habits (around 3000 a year), it's wort it to drop a replacement engine.

Certainly better than the debt.

Ted Leung reports on what he's using to teach his girls about programming:

The new regimen involved another Windows shortcut to pop up Notepad. The girls then had to learn to save a file, switch windows (on purpose, not by accident) to the Python interpreter window, reload the module, and look at the Tk output window. I found myself barraged by questions that had nothing to do with turtle geometry or programming. All the questions were about the environment -- forgetting to save a file, getting windows out of focus or behind each other, forgetting to reload the module, etc. I suppose they were learning computer "literacy", but it really reminded me as to how much stuff you need to know in order to do some simple programming. In a way, it was easier when I was doing AppleSoft Basic on the Apple II -- no separate editor, no windows to lose or have out of focus.

At Mind Camp, Todd Blanchard brought by a copy of "Squeak: Learn Programming with Robots", and the girls got excited by paging through it. It looked pretty good, and Squeak/Smalltalk certainly has the programming constructs that I want my kids to be exposed to straight off (at least if they are going to be programmers). Also, one of the original motivations for Smalltalk was for allowing kids to do programming and simulations, and that heritage seems to have carried through into the Squeak community. For a great/depressing look at some of the learning applications, you can check out this video from ETech 2003.

For teaching software neophytes, nothing stays out of the way and lets you learn like Smalltalk. Which makes you consider the impediments that most people have just gotten used to :)

Via Rob Fahrni, the best example of ironic news I've seen in awhile:

TOKYO, Japan (Reuters) -- Firemen in a small Japanese town were left red-faced after a party to mark the end of a fire awareness promotional event ended in a blaze that badly damaged their station.

The main website at Cincom is undergoing an overhaul, and - as happens with all such overhauls - links to various things have gone missing at some points in the overhaul. Yesterday, it was the success stories, which all reside on the main server. The web team was very responsive though, and it's all fixed now. So if you tried to look at these and got an error, just head back and have a look now.

Add PubSub to the list of search builders that are getting washed and waxed by Splogs. I noted a few days ago that Feedster was getting overrun - most of the results I get from it fall into one of two buckets: ancient, or spam. Troy has had persistent, ongoing issues with Technorati, and he's not the only one.

I think it's clear that we have a major problem, and it's getting to be as bad as the email situation. Search providers are going to have to get serious about building spam filters into their engines - otherwise, we'll see all of the aggregator developers doing it themselves - which will make aggregators more expensive (in terms of system resource usage, not money). It would be simpler if the various providers did the job, because then everyone would benefit, whether they use an aggregator or a browser to view results.

A "Dynamic Language Day" is being held in Brussels (Belgium) next month - February 13th:

The VUB (Programming Technology Lab, System and Software Engineering Lab), ULB (deComp) and the Belgian Association for Dynamic Languages (BADL) are very pleased to invite you to a whole day of presentations about the programming languages Self, Smalltalk and Common Lisp by experts in these languages. Besides some introductory material for each language, the reflective facilities in the respective programming environments will be highlighted. The presentations will be especially interesting for people with good knowledge about current mainstream object-oriented languages like Java, C# and C++ who want to get a deeper understanding about the expressive power of Self, Smalltalk and Common Lisp. In order to prepare the ground for these presentations, Professor Viviane Jonckers will introduce the day by an overview of the benefits of teaching dynamic languages to undergraduate students in computer science. She will especially discuss the specific advantages of using Scheme as an introductory language instead of the more widely employed Java language.

Steve Rubel links to this post, which purports to explain how to get past password protection in a Word document. As Steve said in a caveat:

This post has been updated to imply this is a developing story. It's unclear what this hack exactly does - unlock the read function, the editing function - as commenters on the post have noted

If true - for any kind of password protected Word doc - then it does demonstrate a problem with the ability to export out to straight textual formats. Perhaps protected documents should not allow themselves to be saved into those kinds of easily "hacked" formats?

Via Sam Ruby, I see that Apple has added yet another RSS Module into the mix - Dave Winer has a critique on it here. I added support for it in BottomFeeder this morning; grab the update and the example feeds should give you the extra information. I tried, but I can't get past the irony of Winer criticizing a spec. This is, after all, the guy who inflicted OPML and MetaWebLog *cough* APIs *cough* on us...

Courtesy of Dave Buck, there's a new game available as a BottomFeeder Plugin - Spider Solitaire. It's available as a standard update via the update tool.

BitWorking explains it all. Too bad he didn't have time to sneak a bad word for NTLM-Auth in there.

Slashdot users worry about trivia:

"On the heels of the big Apple love-in that is Macworld comes some interesting but alarming news. Recently a few blogs have started to indicate that iTunes is tracking your music preferences and using that data to recommend other songs from iTMS. The article provides a good overview, with some recommendations of its own. Basically, iTunes is tracking your music and sending the data back to Apple servers. This info is then used to advertise songs that may be to your tastes. A convenient feature, perhaps, but it raises concerns over privacy."

I wonder if Amazon's book recommendations fill them with fear too.

I think Michael Gartenberg has jumped the shark. This week in ComputerWorld, he's comparing the upcoming launch of Vista to the launch of Windows 95:

This is the year of Longhorn -- I mean Windows Vista. Yep, it's real, and it's coming to a desktop near you in 2006. Expect a quiet period in Q1 and then a major ramp-up in the spring. IT won't have seen anything like this since the arrival of Windows 95. While some folks are advising IT to ignore Vista until sometime in 2008, you do so at your own peril. Between Microsoft and its partners, there's likely to be close to a billion dollars spent on marketing this thing. By the time some IT folks get around to looking at Vista, they may discover that users have already taken matters into their own hands.

Yeah, sure. I think he misses a number of things. First off, when Win 95 came out, there was a really, really compelling reason to upgrade: Windows 3.1 sucked, stability wise, and 95 looked like it was going to be a whole lot better (and it was). Now? Windows 2000 and XP are pretty stable releases. Sure, there have been plenty of security holes (WMF, anyone?), but that's true of any Windows product (or OS product, period), and I don't think anyone really believes that Vista will be dramatically better.

So why would I, as an end user of XP, press my IT department to get me Vista? What does it offer me that I don't get now? Nothing terribly compelling, that's what. If Gartenberg thinks that users will rush out and force IT to deal with Vista, he's smoking something. I fully expect Vista to flow in via new PC's, same as any other Windows release. I don't expect to see anyone really jumping for it. Contra Gartenberg, there's no buzz surrounding this. It's too late, and too many features have been jettisoned.

Charles Cook nails the point that I was after yesterday on DVDMaker, managed code, and dogfooding. Yesterday, Dare Obasanjo said:

If Microsoft believed in managed code, we would build applications using the .NET Framework. We do.

[examples omitted]

I find it surprising that people continue to think that we don't use managed code at Microsoft.

That isn't really the problem. It's not that MS doesn't use managed code - it's exactly like the example of the instant-legacy code browser that I brought up in my post - DVDMaker makes it look like they don't use managed code. As Charles said:

Four years after .NET 1.0 was released why has a fairly small scale app aimed at end-users been written in unmanaged code? This app has UI and Vista has a new set of APIs for UI, Windows Presentation Foundation. Maybe its unfair to pick on DVD Maker but this would have been an opportunity, one of possibly many, to demonstrate not only what you can do with WPF but more fundamentally that good end-user applications can be written in .NET. Many people believe that .NET is not suitable for this type of application and a new unmanaged app like this gives them more ammunition.

Exactly. This app being done in C++ is going to raise this kind of question, whether it's fair or not. This is one of those "perception is reality" issues.

I reported a few issues with the NC installer last week - it turned out to be a simple build problem in the installer itself. That was fixed, and an updated set of executables is on the site now.

Another piece of news that should go out - we now have Solaris on x86 VMs available - as part of the NC and commercial releases.

We had a good meeting in Cincinnati today - but boy, when the day starts with a rise from bed at 4:15 am, and you're still sitting in an airport at 10:15 pm, it's been a heck of a long day. Someone invent teleportation already :)

Apple has announced their intel based Macs at MacWorld. Let the drooling begin :)

PVR Wire reports that Tivo to Go is in alpha for the Mac.

Charles points out that Norm Green of Gemstone will be presenting 64 bit Gemstone/S at the NYC STUG on February 1st. Check out their Wiki for details.

The ESUG feed has a long list of online Smalltalk videos - check them out.

Via Cook Computing, I see that MS staff are still pumping out utilities in C++:

4: Is DVD Maker written in managed code?

A: No. Yes, it is ironic that I spent so much time on C# and then spent a ton of time writing something in C++ code. Everybody on the team is a believer in managed code, and we hope we'll be able to use it for future projects.

I'm with Charles Cook on this one - more dogfooding would be a lot more impressive than the hype machine surrounding Vista. Reminds me of a ParcPlace engineer, way back in the VW 2.0 timeframe - he announced (internal mailing list) of his pride and joy - a brand new (code) browser (written in the legacy UI framework). I recall slagging him for it, for the same reasons that Charles posted this: it lets slip the idea that if even the experts still use the old stuff, there must be a reason for it.

Ugh. I decided to take the 5:50 AM flightto Cincinnati this morning so as to avoid an overnight stay. That doesn't seem like such a bright idea now that I'm waiting for the cab :/

Via Steve Rubel, I see that Verizon has decided to take the "oops it was a mistake (damn, they noticed being whispered) about the disabling of MP3 music on their new phones:

Verizon Wireless spoke out Monday after criticisms began appearing on Web logs including PCS Intel and Techdirt regarding the new service, which the company launched last week at the International Consumer Electronics Show in Las Vegas.

Customers wanting V Cast Music who already own one of the two compatible handsets need to visit one of the company's retail locations for a software upgrade.

"Upgrade" my foot :) - it's a restoration of the previous firmware. Meanwhile, verizon claims that it couldn't possibly be to force people to re-purchase stuff they already own:

Verizon dismissed accusations on certain Web logs that this decision was made for any ulterior profit motive such as forcing users to repurchase music through the V Cast store.

Instead, the company said, the MP3 capability was temporarily disabled so that it can be integrated into the V Cast application, rather than appearing as a separate application that might confuse customers.

Yeah, right. And I'm the Queen of Romania.

Via Rob Fahrni, I found this truly bizarre CNN story - a man tried to burn a mouse, and lost his house instead:

A mouse got its revenge against a homeowner who tried to dispose of it in a pile of burning leaves. The blazing creature ran back to the man's house and set it on fire.

I'm getting flashbacks to those margarine ads from the 70's - the ones where the woman (playing Mother Nature) would taste the margarine, and then say (ominously) "It's not nice to fool Mother Nature" when she was informed that it wasn't butter...

David Buck is offering a two day introductory course:

I keep hearing people say that they'd like to learn Smalltalk but don't want to sign up for a full 5-day Introduction to Smalltalk course. I decided that it would be a good idea to have a quick 2 day course showing what Smalltalk is all about. This course is aimed at people who don't necessarily expect to work professionally in Smalltalk after the course but who want to learn more about object oriented programming and how it's done in other languages. I'll be holding the first run of the course in Ottawa on February 16th and 17th, 2006.

Via Glenn Vandenburg, I came across this post from Reginald Braithwaite-Lee. It's all good, but there's a really, really good summary in there, where he explains why Rails is hot and Seaside isn't (yet):

Speaking of Rails, I'm going to conclude with my take on one reason why Rails is taking off and Seaside is not. Rails allows programmers to express the idioms they already know (relational databases, web-backed MVC, stateless event handling plus a global session store) in fewer bits.

Seaside provides a whole new idiom, continuations, that IMO is more powerful. I think you end up with an even higher signal-to-noise ratio with a Seaside app than with a Rails app. Why? Because continuations afford you a much higher degree of controller reuse.

Now, here's the catch: if you try to imagine your current application running on both Rails and on Seaside, you probably won't see much difference between the two (although they'll both be an order of magnitude better than ASP.NET). They will look the same because you designed your application with idioms that both Rails and Seaside support.

I think that captures it perfectly. What we (in the Smalltalk community) need to do is show Seaside (or something else in Smalltalk) solving a common problem in a dramatically easier fashion - as Rails has.

The Security libraries in VW 7.4 have been cleaned up a lot - but some of that might affect backward compatibility. This server is still running on VW 7.1, for instance - I had to do a small bit of work (with Martin's help) to get things to interoperate between the two.

Back in 7.3 and prior versions, here's how I encrypted a string using DES:

	des := DES new.
	cypher := des encrypt: plain with: key.

Now, in 7.4, there's been an API change. The #encrypt:with: method no longer exists. So it looked like all I had to do was this:

	des := DES newBP_ECB.
	des setKey: key asBigEndianByteArray.
	cypher := des encrypt: plain asByteArray.

However, there was another change that this didn't account for. When the Security libraries first came in, they were rushed out the door - the code was hard to follow, and there were other issues. That's cleaned up in 7.4, but it was smacking me in the head for backwards compatibility. After a conversation with Martin, it turned out that the padding scheme used in 7.4 was correct, and that older versions had used something else. To get it to work, I juist had to wrap the DES encryption with the same kind of padding:

	des := SSLBlockPadding on: DES new.
	des setKey: key asBigEndianByteArray.
	cypher := des encrypt: plain asByteArray.

And it all worked. Which means, I can now put together a dev build of BottomFeeder using 7.4. I'll get to that later today, or possibly Wednesday (I'm heading to corporate for meetings tomorrow).

If you're in the LA, the STUG is meeting this evening.

Blaine reports that the Omaha Smalltalk and Ruby groups have decided that they have a lot in common - so they are combining:

The Smalltalk and Ruby user's groups have been combined into the new and exciting Dynamic Language User's Group. The new group will be about all dynamic langauges. So, we'll be talking about a lot of languages. The first meeting will be on February 7, 2006. Our first topic will be DynAPI which is cool Javascript open source project and presented by Brent Adkisson. Our meeting place and email list has changed too. I hope to see everyone! Sign up for the new list!

Vorlath should look at Seaside, and the concept of Continuations. Bottom line - been there, done that.

Something else I just can't understand is why source code doesn't have rollbacks. Let's say I allocate an object, then I open a file, but then some kind of error happens on the third statement. How many times do we have code in C (or any other language) to check for allocation, then check for NULL on the file and delete the previously allocated object if the open file command did return NULL and so on getting bigger and bigger. We need a rollback command. Some kind of code attached to all sorts of commands so that it can go back to a previous state. Rollback code for allocation should be deallocation. Rollback code for opening a file should be to close it. Most of this should be default and supplied by the library. So if an error happens, we can rollback to a more stable state. And all this should be hidden away from normal view. If you want to change the way it works, then fine. But it shouldn't clutter the main code. It boggles the mind how backwards we are when it comes to programming. Databases have it. Why not code?

Watching the Bengals game, the best I could figure about the second half was that the studied film from the second half of the Giants game. Boy, did they fall apart.

Jeremy Zawodny thinks that Feedster is toast, but Technorati will be fine. I agree with him on Feedster; the amount of broken HTML and spam in the search feeds I use has been horrible. On Technorati though? He needs to talk to Troy.

Via Doc Searls, I see that Microsoft and Verizon have learned nothing from the Sony affair. I guess disabling features counts as delighting your customers, eh Scoble? Then again, these are the people who want to ram the PVP-OPM down my throat, so I shouldn't be surprised.

The game isn't over as I write this, but it may as well be. A botched punt return at the end of the first half allows a field goal. A stupid pass at 6:30 left in the third yields an interception and a touchdown. The offense has been asleep at the hike when they haven't been trying to give the ball away. I guess the only consolation is that Carolina won't get far if they play this way again; they should be up by 4 or more touchdowns with how they've dominated time of possession.

Sigh.

Update, end of game: Here's how I imagine the half time speech in the Giants locker room: "Guys, we mostly sucked in the first half. If we work at it, we can completely suck in the second half!"

Troy is pretty darn torqued at Technorati (read the post to see why) - and his post is an example of something I've spoken about a lot. Word of mouth carries a lot further than the break room these days. When you ignore problems long enough, they don't just go away - they start generating negative PR. For those without a cluestick, take a look at Dell Hell for instruction.

It's time to find out whether the 11-5 Giants are for real, or a fluke. Two weeks ago, they fell apart against Washington - a team that looked completely ineffective against the Bucs yesterday. What you have to realize about that Skins game is that their offense only managed 3 points by itself - the defense scored one touchdown, and laid the other one at the offense's feet. Which is why I wonder about the Giants - they let Washington walk all over them.

I guess I'll find out this afternoon. At least there's a playoff game I have some interest in to watch.

It's time to look at the logs again - last week, BottomFeeder downloads held steady at a rate of 352 per day. The details:

Platform	BottomFeeder Downloads
Sources	651
Windows	499
HPUX	474
Mac 8/9	291
Update	144
Linux x86	144
Mac X	113
CE ARM	61
AIX	19
Windows98/ME	18
Solaris	17
Source Script	13
Linux Sparc	10
Linux PPC	7
SGI	3
ADUX	2
CE x86	0

I'm not sure why the source downloads jumped up - I haven't released a new build recently. Anyway, off to the HTML page accesses over the week:

Tool	Percentage of Accesses
Mozilla	53.4%
Internet Explorer	26.7%
Other	7.7%
MSN Bot	6.8%
Google Bot	3.2%
BottomFeeder	1.2%
Opera	1%

Back to Mozilla being on top, which is more like my normal distribution - that likely means nothing more than a return to work after the holiday season. On to the RSS accesses:

Tool	Percentage of Accesses
Mozilla	24.4%
Other	5.3%
BottomFeeder	21.2%
Net News Wire	9.1%
BlogLines	8.7%
Safari RSS	5.4%
Internet Explorer	4.3%
SharpReader	2.7%
Magpie	2.3%
RSS Bandit	2.1%
Planet Smalltalk	1.8%
NewsGator	1.6%
Feed Reader	1.4%
Liferea	1.3%
BlogSearch	1.2%
MSN Bot	1.2%
Java	1%
JetBrains	1%
News Fire	1%
Python	1%
Feed Demon	1%
Google Bot	1%

Now, that looks like a sudden jump in BottomFeeder usage, but it's not. I looked at the "other" category, and I had forgotten that a few revs of Bf have gone out with an agent string that differs from what I've been looking for in my script. So, the numbers for Bf access should be increased by around 10% (and "other" marked down) for the last 6-9 months or so. Ahh, statistics :)

Bob Congdon links to Dave Delay, a former Lotus Notes Developer. Dave is upset that many people seem to hate Notes, and is attempting to counter that:

In my opinion, people dislike Notes because their expectations don't jive with the original intent of the product. At its core, Notes is a runtime environment for collaborative applications, but when people complain about Notes, they are usually not talking about core Notes at all. They are talking about the Notes Mail and Calendar applications. Why does this distinction matter? It matters because the Notes core is what a lot of people really love.

Bob goes on to explain the issue, and it's something that resonates with me. I love Smalltalk, and have for years. I get the same kind of "huh?" reactions that Bob brings up on a regular basis, and it has to do with expectations.

Smalltalk, for good or ill, has a culture surrounding it. That's not really true of C, or C#, or Java (or most other languages, including newish ones like Ruby or Python). Smalltalkers don't work in their favorite code editor, followed by a compile cycle. We work in an image, crafting code one method at a time in a browser. We don't look at long listings of class definitions and methods; we look at little snippets of our system through the browser, and rely on inspectors and ad-hoc workspace testing (not to mention more formal testing) to "see" the code. Which is to say, our development culture is different than what the mainstream developer expects.

When a developer who's heard a lot about Smalltalk - perhaps after having seen Ruby or Python - can be somewhat taken aback by this culture. All their familiar tools are gone; the version control systems are unique to the product, and the development tools are embedded in the environment. We, as Smalltalkers revel in that - we understand the power this brings, and want no part in leaving it. The newbie, on the other hand, sees a learning curve and an inability to apply previous skills to the task at hand.

Which is why there's a disconnect between the Smalltalk community and the development community at large. Now, many would say that we should just "get with the program" and make our stuff look like everything else. The trouble is, that would jettison a goodly proportion of the power we have - the cost is simply too high. We could do a better job of introducing people to the environment, that's for sure. But I don't think we can walk off the mountain and be like everyone else.