Smalltalk Tidbits, Industry Rants

Doc reports that Neville Hobson is seeing his RSS feeds "hijacked" from a hotel. I suspect that what's happening is that Neville's network usage has expired, and all http requests are being redirected. I've had that happen before.

Yep, I just browsed his post. Look at the url that his feeds got redirected to: "http://soln-sr965.solutionip.com/register/"

I've definitely seen that before. What he got bitten by is a bad implementation of redirect by the hotel's ISP. The redirects should be temporary, but I bet they are all permanent. FeedDemon, like BottomFeeder, sees a permanent redirect on a feed and silently adjusts the properties for the feed in question. Very nasty - at hotels that have network service that I need to resubscribe to daily, I always take BottomFeeder offline when I go to sleep. Time for Neville to look for backups...

By now I'm sure you've seen the IBM announcement on VisualAge Smalltalk, and the Instantiations announcement as well - the latter being a future roadmap for VA from Instantiations. We've been aware of the coming end of life for VA (at IBM) for awhile now, and have been talking to partners about providing a roadmap for interested developers. We don't have anything specific to announce that way today - but we will shortly. Expect to hear something concrete by the time of Smalltalk Solutions 2005 in Orlando.

What should you take from these announcements? First off, you should take a fresh look at Cincom Smalltalk - it's cross platform (including multiple Linux platforms and Windows CE). It's binary portable. It's a full software stack, supporting modern standards like WS*. It includes two premier Smalltalk environments - VisualWorks and ObjectStudio. Cincom is fully committed to Smalltalk - we have the largest staff of developers of any Smalltalk vendor, and have been doing more forward development than any vendor. If you want a stable, secure platform that is under active development by many of the leading luminaries in the Smalltalk world, then you should download our product and have a look.

How do you know that we are committed to our product? We are profitable (both Cincom as a whole, and the Smalltalk business inside it). We are also eating our own dogfood - the main Smalltalk site is a VW ssp driven site, as is this blog server. The various services provided on this server (surveys, downloads, the Wiki) are all Smalltalk powered. We believe in our product enough to use it.

As I said above, we'll have more to say on this shortly - in the meantime, you'll be happy to know that a move to Cincom Smalltalk won't include any so-called "modernization" materials advising you to migrate to less powerful and more expensive technologies. Questions? Feel free to comment, or send email to Suzanne Fortman (our Smalltalk marketing manager), or me.

James Governor points to what could be the beginning of actual watchdogging between analysts and journalists. About time, I'd say :)

BusinessWeek's new blog has gone after Laura DiDio, Yankee's Get The Facts lead. Laura has long been a target of Linux lovers, for her uncompromising defence of the proprietary. But BusinessWeek writer Steve Hamm aims to expose limitations in Yankee's research approach. It will be interesting to see if a story appears in the print edition; it has to be likely. If you want to contact me for the article Steve i would be more than happy to contribute. I tend to pretty vocal on the subject of industry analyst ethics, and RedMonk is doing the best we can to do the right thing.

I've added tentative Atom 1.0 support into the dev stream of updates in BottomFeeder 3.9. I'm not going to promote it to the non-dev stream until one of two things happens:

• The format starts getting used "in the wild" (which happened with 0.3)
• The format gets stamped final

In the meantime, the dev stream only support should be considered tentative - and I'd appreciate any bug reports from people who see it (Atom 1.0) being used.

Register for StS 2005 today - it's coming up fast! Here's today's spotlighted talk:

A Smalltalk-based system for dynamic multi-context information processing experience report

van Os, Adriaan and Westerhof, Eugene: LEI - Wageningen UR

Monday 4:45 pm to 5:30 pm

Abstract: In spite of the dynamic character of information need, software systems should preferably be stable. Software changes are expensive and are a risk to system stability. This is why we want to separate the software engineering process from the information systems development activities. For this purpose LEI developed a Smalltalk-based system for model-based system specification and workflow management. System behavior is dynamically generated from data specifications, constraints, computation models and workflow specifications. In our presentation we will explain the construction of the system and the main principles it is based on. We will demonstrate how context-independence of the data model has been achieved and how the workflow engine schedules the workload.

Bio: Adriaan van Os

• Working with Smalltalk, mainly VisualWorks, at Soops since 1995.
• Main architect/developer of the presented system.
• Involved in some CampSmalltalk projects.

Eugene Westerhof

Developer of several subsystems of the presented system.

See you in Orlando!

In a Red Couch interview, Jonathan Schwartz put his finger on how blogs change the nature of interaction between journalists and the rest of us:

We asked him what blogging’s role will be in this new Era.

“It’s kerosene on the fire. The Participation Age has been on the Net since email. Moving from there to blogging is like moving from carrier pigeon to phone. The emergence of blogs means we have passed beyond early crude tools and it results in fundamental changes on how everything relates. While a journalist is writing about my blog, I’m blogging about his journalism. This is change,” he told us.

In a very real sense, blogs are the new "letters to the editor" - only the editor has no choice as to whether it gets printed. There's still no guarantee that you'll get more than trivial readership, but it's a far, far better chance than you had with the letter.

Here's an interesting interview with Al Ries, author of "The Fall of Advertising & The Rise of PR." Cincom's Steve Kayser asked him a few good questions about advertising and PR - I liked this summation of things:

Steve: So when it comes down to bottom-line ROI?

Al: No-brainer. The largest advertised brand in America spent $780 million on advertising last year. Do you know the name of the largest advertised brand? It's not McDonald's, Budweiser or Coca-Cola.

The largest advertised brand in America last year, would you believe, was Chevrolet. Now let me ask you a question, what's a Chevrolet? If I told you I would meet you out front in my Chevrolet, would you be able to recognize my car?

What's a Chevrolet? A large, small, cheap, expensive car … or truck. But you already knew that. $780 million and there probably isn't one thing stuck in your mind that you can connect with Chevrolet. What a waste.

His point is the large scale advertising is often a symptom of trouble (think about companies that went into bankruptcy recently), or a sign that a company hasn't got any good brand recognition - and advertising isn't going to solve that problem. A good ad campaign can complement good PR, but it can't salvage bad or non-existant PR. You need something to build on, first.

Read the whole thing - there's more good stuff there.

It's time for my weekly log scan again. I've gathered up the XML stats, the BottomFeeder download stats, and the general HTTP access stats to see what's what. Here's what's happened since the last look on the 19th (roughly 7 days, given the cutoffs):

Platform	BottomFeeder Downloads
Windows	633
HPUX	491
Mac 8/9	412
Sources	341
Linux x86	232
Mac X	217
CE ARM	130
Windows98/ME	76
Update	58
Linux Sparc	22
Solaris	16
Linux PPC	8
AIX	7
SGI	5
Source Script	4
ADUX	3
CE x86	0

The totals? Add it up and we get 2655, or nearly 380 per day in that time span. Not bad - although I have no clue why there are so many HPUX downloads. That's got to be some kind of anomaly :) The Mac 8/9 rates still outpace OS X by nearly a factor of 2, so rumors of that rev of Mac OS' death are greatly exaggerated. Next up: A look at what tools are looking at the RSS and Atom feeds:

Tool	Percentage of Accesses
BottomFeeder	21.8%
Mozilla	19.6%
Net News Wire	16.4%
Other	13.4%
NewsGator	4.6%
BlogLines	4.3%
SharpReader	4.3%
Internet Explorer	4.1%
Planet Smalltalk	2.3%
Feed Demon	1.9%
RSS Bandit	1.3%
JetBrains	1%
Liferea	1%
Shrook	1%
Magpie	1%
PubSub	1%
Feed Reader	1%

The stats here look mostly the same as they have the last few times I've checked, which is no big surprise. Unless I get some big up or down spike in readership, these percentages aren't likely to shift a lot. last up - the HTTP accesses to the site:

Tool	Percentage of Accesses
Mozilla	54.4%
Internet Explorer	33%
Other	10.6%
Opera	1%
BottomFeeder	1%

Those are a bit higher for the straight browsers than they were last time. Otherwise, Mozilla based browsers continue to dominate over IE (which is why I figure I get so few MSN searches in my referers).

Sci Fi Wire reports that the brain freeze affecting Star Trek's writers shows no sign of abating:

Star Trek: Enterprise producers Brannon Braga and Rick Berman told SCI FI Wire that they understood the recent disparaging comments made by cast members about the final episode, but stood by their execution of the series finale. "You have to remember, under normal circumstances, most people probably would have thought this was a very cool episode because it has a great concept driving it," Braga said in a conference call with reporters. "But when it's the final episode of a series, emotions are running very high."

Yes, this last season has been much better. In fact, had they had stories like this the rest of the time, the series wouldn't be ending. Having said that, it's kind of a hot tip when your cast is willing to be publically quoted bad mouthing the finale. And well they should - the finale involves Frakes and Sirtis (Next Gen) watching the Federation ceremony via the Holodeck. The Holodeck? Good gosh, that's the place the writers went when they had no ideas left! Berman was facing the end of Trek on TV for the first time in over a decade, and the best he could come up with is a Holodeck episode?

If Paramount wants to revive this franchise, they need to retire Berman. Send him off to wherever George Lucas has been for the last few years, so that they can have bad sci-fi ideas together, and leave the rest of us alone.

Dvorak has been "out standing in his field" for awhile now, but this latest column has an item I just can't pass up:

Power plugs on airlines. Has anyone but me noticed that most of the airlines that have power plugs fitted into the aircraft have stopped using them? A couple of years ago, they were all active, although none of us had the little connectors. Now that we have the connectors, the airlines have shut down most of the outlets. In the past year, I have not been on an airplane that has had these systems running. What happened? Were they blowing up? Catching on fire? This was a DC system, so people couldn't have been electrocuting each other. I have yet to get an explanation for this, except for typical airline apathy.

Hmm - I've flown multiple airlines with power over the last year or two, and I can only recall two things - the power being left off by accident (i.e., the pilot not turning it on, and having that corrected by talking to a flight attendant), and having a faulty power outlet at my seat (only seen that once). And yet here's Dvorak, claiming that no flight he's been on has had working power. Hmm. I suspect a wee bit of exaggeration there. He must live on a different planet...

Update: Gordon Weakliem reminded me that LiveJournal does support digest auth for feeds - there are details on this page. So just ignore my wild eyed ranting about LiveJournal below :)

Yesterday, I had someone ask me if it would be possible to support the private feeds LiveJournal uses. He set up a feed that had password protection so I could test - that's when I started the slow slide into "standards? what standards?" hell. First up - LiveJournal. Could they use Http Auth or Digest Auth for their private feeds? Nope, that would be entirely too simple. Perusing their forms, it looks like they use their bozo equivalent of Digest Auth, but only if you pass through their form and retrieve a cookie. Retrieving the cookie would "just work" if they used Auth, but nooo - they have to be special.

So off I went, to add support for that. Strike two came around the corner shortly thereafter. I couldn't read their cookies, because they use a non-standard format for them. Great - seems the New York Times does the same thing with their cookies, so maybe there's a common content management system out there with bad ideas. One AR later, and a discussion with the VW developer who works with this stuff and I had a fix.

So now, a full day later, I can actually start looking at actually supporting LiveJournal. It's things like this that make me laugh at the "Atom will solve everything" crowd. A new spec won't change the fact that people make mistakes and refuse to follow standards...

Scoble notes the progress towards making PC's "dull" (in the sense that TVs are dull - that they "just work"):

Scott Koon is bored by all the stuff he saw come out of Winhec yesterday. Or, more accurately, he's ambivilent. I can understand that. Sometimes computers seem as exciting as cable TV, electricity, or water.

Well, we aren't there yet. Sadly, we aren't even close. When I visited LA recently, I spent a decent amount of time securing my wife's cousin's PC. I'm on the hook to visit one of her co-workers, so that I can do the same there. The trouble is, most people want to treat a PC the way they treat a TV. That's just not feasible yet. You need anti-virus protection, you need a working firewall (in addition to the NAT protection offered by a router), and you need anti-spam software. My wife was commenting the other day that she couldn't get email while my daughter was present.

Is all of this MS' fault? No, it's not - but they bear a fair bit of the blame for having whistled past the graveyard on security for years. We're going to be paying the price for that decision for years, as we wait for Windows 98/ME to die off.

I should have mentioned that yesterday was Anzac Day in Australia and New Zealand. When I visited Australia last year, I visited the war memorial in Sydney (which, sadly, was sealed up - apparently, antiwar protesters kept defacing it. Utter lack of respect, IMHO). I also visited the huge memorial in Canberra, which looks a lot like the mall in Washington (DC) - only with red sand rather than the reflecting pool. So a day late, I'll give a tip of the hat to the memory of all the brave Aussies and New Zealanders who fought and died for their countries.

Scoble stopped patting himself on the back over the anti-discrimination imbrogolio long enough to ask an interesting question:

That gets me back to something else I've been thinking about. How do you rate search engine quality?

But, it is pretty interesting that all three engines have as a #1 result something I wrote on Saturday (although you'll see MSN biases against blogs). I remember the days back in 1996 when I tried for more than a year to get Yahoo to list a site of mine, and even Altavista used to take more than a month to list new information.

He's right about the engines picking stuff up faster, that's for sure. There's been some level of pressure on Google (et. al.) at the bleeding edge from blog specific engines (Feedster, blogdigger, etc.). That's helped push them towards getting new stuff up faster.

I'm still kind of amazed at how few refs I see to msn searches on this server though. My referer lists are full of Google, and always have a few Yahoo requests. There's almost never an MSN request though. Very few of my readers are using MS' search engine, that's for sure. As to why that is, I suspect that it's related to the high usage of Mozilla I see. Firefox comes with a Google search field right in the toolbar, which means that I rarely bother with any other search engine. My guess is that most other Firefox users follow the same usage patterns.

It's amusingly ironic, seeing MS beaten at its own embedding game that way.

Slashdot points to what you have to call Extreme Gaming:

"Wired reports about four skydivers who decided to give the Nintendo DS wireless capabilities a try while they were freefalling. 'The four sky divers proved that an ad hoc network set up using the wireless functions of a Nintendo DS works perfectly at distances of nearly 400 feet while falling 120 miles an hour,' states the article."

Lileks has a fun bleat up today - the part that really struck me was his experiences with a couple of vendors (Best Buy and Marshall Fields, but it could be any large corp.). The trouble he ran into is common to companies where individual employees have no stake in the results - the Dilbert problem of "the pay's the same no matter what I do". Here's the punchline:

Lesson: from Best Buy to Marshall Field’s, it’s the same problem. One day a company is responsive, quick, savvy. Then one day it’s one percent bigger than it was before, and something happens. They’re the IRS. They’re the Pentagon. They’re an organization slowly ground into ruin by a thick busy level of managers, some of whom are in charge of extracting point-of-sale contact info, others who are going to make their bones on a store-wide phone-system overall. Elephants playing patty-cake.

When the people you deal with have no idea why they are asking the questions they ask, it ends up being a problem. Something to consider at acquisition time, I think.

Some folks from Quallaby are putting together a STUG in Boston - check it out, as they meet tonight - Colin Putney put out an announcement:

The Smalltalk group at Quallaby (where I work) is organizing a get-together of Smalltalk folks in a couple of weeks. I'd like to invite all Squeakers to the first meeting of the Boston Area Smalltalk Users' Group. There's no agenda; the first meeting will be to gauge interest, get to know each other and plan further activities.

BASTUG Inaugural Meeting:

Monday, April 25, 2005, 7:30 pm.

Not Your Average Joe's (coffee shop)

1727 Massachusetts Ave, Lexington, MA

If you're in the neighbourhood, drop by and say hello. Feel free to contact me off-list if you need more information.

Here's a headline you don't see every day:

Exploding Toads Baffle Experts

Today's update looks at Software Components in Smalltalk. Register today!

Programming with Software Components: From Globals to URIs, Classes to Interfaces

presentation

Staehli, Richard: Simula Research Laboratory

Monday 4 pm to 4:45 pm

Abstract: Component-Based Software Engineering (CBSE) promises to simplify the construction of high-quality applications through composition of off-the shelf components. This is arguably a fulfillment of the original promise of object-oriented programming; that objects may encapsulate arbitrary implementations.

Surprisingly, the Smalltalk community lags behind the industry in advancing CBSE technology. The idea of composing a computing system from components that may encapsulate heterogeneous programming language and runtime environment is at odds with Smalltalk's single image heritage. Further, todays component technology, such as CCM, force a programmer to choose when to use heavyweight components and when to use lightweight local class instances.

Our investigation into a Quality-of-Service (QoS) -aware component architecture suggests a way to improve Smalltalk programming by separating concerns of functional composition from concerns of component implementation. In this presentation I show how Smalltalk source code may be made more robust by replacing a global reference to an implementation class with a Universal Reference Identifier (URI) for a component interface type. This allows the implementation of this component to be determined at compile time, deployment time, or even upgraded dynamically at runtime without violating the semantics of the source code.

Bio: Richard Staehli has worked the past three years architecting and prototyping a Quality-of-Service (QoS) -aware component architecture in Smalltalk for Simula Research Laboratory in Oslo, Norway. He received a Ph.D. in 1996 from The Oregon Graduate Institute of Science & Technology and has since worked on video data types for Informix Software, on a CORBA application server for Oracle Corporation and as a senior technical consultant for the interactive web services firm AGENCY.COM .

See you in Orlando!

For those observing Passover (or like me, married to someone who does) - the Jib-Jab treatment of Matzah is a must-see. Yes Virginia, there certainly is such a thing as too much matzah :)

There's a small bug fix out for the 3.9 release of BottomFeeder available. As it happens, the http code was making an incorrect assumption about getting encoding information from XML documents. It was assuming that every header with encoding information would wrap the encoding in double quotes (as HTTP attributes normally are). A quick perusal of the specs shows that this is a bad assumption - the encoding can be wrapped in single quotes. The latest update for the NetResources library addresses this. The symptom? There are some feeds that weren't being read at all, and others that were being badly decoded (i.e., you would see occasional odd characters).

Jonathan Schwartz hasn't gotten the memo yet - "the network is the computer" was the pitch about 8 years ago. Here he is again though, flogging network computers:

Display over IP. DOIP ("Do IP") is to the PC industry, what VOIP (voice over IP, simplistically, using the internet to make phone calls) is to the telecommunications industry. Phone calls are near to free at this point, and the business model is undergoing radical change. It's inevitable that pervasive and sufficient bandwidth will allow most of what happens on a client to migrate to the network. Why upgrade your PC if you can rely on plentiful bandwidth to have someone centrally deliver it as a service? You don't upgrade your TV set, BBC and News Corp do it for you every evening with fresh content. And you don't buy a new TV to watch it. The same should apply to your PC. DOIP is to a PC as XMRadio is to a CD player.

Sure it is. You come down here and deal with the "DNS? What's DNS?" service that Comcast is becoming known for. A couple weeks of that will wash this bad idea clear out of your head.

And I don't upgrade my TV set? Good gosh, which part of HDTV haven't you heard about? To get improved content, I have to upgrade both my TV (done) and my cable box (not yet) - and my ReplayTV as well. The most irritating part of his post is the way he's trying to wrap a pure marketing ploy (please, buy useless network PC's so that I can sell a ton of expensive Sparc boxes to datacenters) in environmental clothing. Sheesh.

PR Opinions unearths the unseemly practice of paid advocates - the kind that you don't hear about as having been paid:

Appearing on a local TV show in Austin Texas to review toys for kids, Oppenheim promoted a number of different products including a  personalized photo album from Eastman Kodak.

The only problem was that Mr. Oppenheim was paid by Kodak.

On a subsequent appearance on NBC's Today show, he once again promoted Kodak's product - though Kodak says it didn't pay for that particular mention.  That was obviously Oppenheim's favor to Kodak. And they weren't alone.  Of the fifteen products he plugged on NBC, nine were former clients and eight had paid for plugs on local television.

The Oppenheim episode has opened up a big can of worms.  It appears that there's a booming industry for TV talking heads promoting products for cash with no disclosure before, during or after their segment.

Infomercials are better than that - at least they don't hide the pitch. It's only a matter of time before this happens in the blogosphere (more likely, before it gets reported as happening). There have been bloggers paid for political mentions (from both sides of the spectrum) - I'd guess that there are bloggers getting paid for product mentions as well. Easy enough to do, actually - a blogger with a passion for something (photography, say) gets offered money to slip in mentions of a particular brand/model. I don't see any obvious way for general readers to find out, either.

Bob Congdon points out that Coke cans do, in fact, have value!

I just finished another one of the histories of WWI that I've been immersing myself in - this one is "The Illusion of Vistory: America in WWI" by Thomas Fleming. It covered a shorter period - just the time from American entry in 1917 through the end of Wilson's presidency. It's a fascinating study of the politics that surrounded American entry into the war, and the attempt by Wilson to get the League of Nations treaty passed. The thing that really struck me was that pride and self righteousness was most of the problem. Wilson was not only sure that he was right - he was convinced that his political opponents were not only wrong - they were evil for disagreeing with him. Needless to say, that made it pretty darn hard to compromise with the senate - and compromise with the senate is the only way for Presidents of the US to get treaties through.

The other thing that I found interesting was the more US focused background on the peace conference. The last book I read - "Paris 1919: Six Months that Changed the World" - wasn't focused on Wilson and the US delegation. It covered the conference in exhaustive detail, while Fleming's book merely skimmed it. Even so, in covering the interplay between Wilson, his wife, Colonel House, and the other important US players, it filled some interesting gaps. Fleming comes down pretty hard on Wilson - but at this point, with all the reading I've done on the subject - I think Wilson deserves a fair bit of opprobrium.

In any case, "The Illusion of Victory" is a worthwhile addition to any study of WWI - especially if you are interested in the US effort. Next up is Barbara Tuchman's classic, "The Guns of August". After that, I think I'll tackle Nicholson's book on the Congress of Vienna.

Two sedars in two days is a sure-fire way to be fully, totally stuffed. It's like back to back Christmas dinners, only without the dinner rolls. Oof.

One of my readers sent me a link to this article on "duck typing" (i.e., what Smalltalkers have called dynamic typing for eons now). Here's the part I found incoherent:

First of all, let's get a frequently asked question out of the way: if two interfaces have the same methods, are they semantically equivalent? Isn't there a risk to pass an object that is totally wrong for this method, yet will work because it responds to the right methods?

I don't have a clear answer to that, but my experience is that such a thing is very unlikely. This kind of argument is a bit similar to the fear we all felt in the beginning of Java when we realized that containers are not typed: ClassCastExceptions end up being much more rare than we all thought.

Duck Typing is a big time saver when you write code, but is it worth it? Don't you pay this ease of development much later in the development cycle? Isn't there a risk that you might be shipping code that is broken?

The answer is obviously yes.

So the sorts of errors the author fears are virtually non-existant, but they introduce a huge risk of shipping broken code. Excuse me? Is it just me, or is the author arguing with himself here?

One of the things I really like about this mode of argument is that testing isn't sufficient - we need something stronger (enter declarative typing). If that's the case, why do people writing in C++, Java, or C# even need to test? Doesn't the typing obviate the need for it? The point is, you need to test anyway. If a given paradigm - dynamic typing in this case - increases productivity - and if declarative typing doesn't obviate the need for testing (it doesn't) - then what does the typing buy you? Better arithmetic performance, mostly. That's useful for a small range of applications (and, for most of those, we can use a high level language like Smalltalk and mixin lower level languages for the performance critical sections. Plenty of our customers do just that.

The author comes up with a contrived example to show that declarative typing will save you from a potential runtime nightmare. I say contrived because I've written code using the kind of API he talks about many, many times. Want to know how many times I've walked into the minefield he fears? It's a small number, except for the larger values of zero.

The best part of the whole thing is the comments, where some of the responders claim that refactoring tools are "impossible" in languages like Smalltalk. Times like this I wonder how many people realize that all the cool stuff that people think came from Java - like refactoring support and unit testing - were invented in Smalltalk more than a decade ago.

I swear, this entire industry actively engages in amnesia...

Frank Patrick talks about scheduling a delivery, and relates it to a scene in an HBO movie about the Apollo program:

"Schedule Chicken" is one of my favorites. If you've ever seen the HBO Series "From the Earth to the Moon," about the Apollo program, you might remember what was my favorite episode -- the one about the Grumman engineers building the lunar lander. There's a great scene in which everyone goes around the table saying "Sure, my group's on track." until one admits the reality of needing some more time, at which point everyone then backtracks, saying, "Well, since Joe will need more time, we could use it to..." There's other PM wisdom and reality spread out in that episode. Check it out if you get a chance.

I see this every release schedule here. Towards the end, we have release meetings where we go over the high and critical bugs. The idea is, engineers who have a bug that needs fixing prior to release have to get dispensation from the rest of the team - either by explaining that there won't be a regression, or that the bug is so bad that we have no choice - you get the idea.

Towards the very end of that exercise, we start doing candidate builds. When there's something wrong in a candidate build, I see the same reaction Frank mentions: "well, so long as we are cracking the build, can we sneak this in..." - comes up every release cycle.

Sounds to me like this sort of thing is endemic to all engineering work - both hardware and software.

Michael thinks that MS will eventually beat out Google - his reasoning being twofold:

• Word of Mouth is the only advertising gets, whereas MS is all over the air
• With Longhorn, MS will embed search to an extent that people will get driven to their site

That's certainly possible. On the other hand, Longhorn adoption is going to slow. Why? Because XP is, for the most part, good enough. Unlike 95/98/ME, it doesn't crash every time you look sideways at it. Then there's the advertising angle - and if the MS Office "dinosaur" campaign is any indication, I don't think Google needs to quake in their boots yet.

Current search engine use can't be terribly comforting to MS. When I scroll to the bottom of my blog, I find the daily (updated every couple of hours) referers. There's always a ton of hits from Google searches. There's usually one or two from Yahoo. It's a rare day when I see an MSN search result there. Heck, I may see Ask Jeeves more often - possibly even AltaVista.

There's not going to be a free Longhorn based swap-over, I don't think. If MS wants to win in search, they're going to have to do it the old fashioned way - provide a better set of results.

Slashdot reports that Borland is giving JBuilder away on Eclipse now:

"The Register is reporting that Borland has released the base version of JBuilder as open source on Eclipse! Is this just the next company to use open source as part of a marketing tool, akin to Sun, IBM and Oracle's opensource IDE push? Is the future of enterprise IDE open?"

So my question is: What's the revenue model (for Borland) behind this? Too many people look at open source as some sort of good/evil divide - at the end of the day, the more important question is: where the revenue comes from - no revenue, no business...

If you want to see a nice roundup of the method lookup post I did a couple days ago, have a look at the comments - especially the ones Loryn Jenkins put up. Nice set of comparisons there!

Looks like tonight's dinner will be broiled (oven) steak instead of grilled - thunderstorms and rain just aren't conducive to enjoyable grilling. Sigh...

Derek points out some of the weak thinking at the TSA with a personal example. The last time I ravelled, I had something else occur to me in terms of threats - the huge backup in front of the security zone. Think about it - there's the TSA, asking you to remove your shoes, take your laptop out of your bag (and going on breaks in the face of huge lines, but never mind that) - the whole dreary experience. The result is a huge line in front of security, and most airports have reacted to that by putting in theme park style maze lines.

Now look at that situation. If you really do want to commit an act of terror, do you care whether the dead bodies are on the plane or not? What the TSA has unwittingly created is a target rich environment in front of the screening area - a huge mass of compliantly waiting, penned in people with nowhere to go. I can't wait to see what stupidity the TSA comes up with after this gets exploited by a bad actor somewhere.

Steve Rubel points to an excellent piece of marketing by Major League Baseball - they are sponsoring fan blogs:

Major League Baseball is now empowering consumers to launch their own Six Apart-powered blogs. The MLBlogs site is live. Users can sign up for $49.95 per year. Tommy Lasorda's even blogging. The former LA Dodgers manager has comments turned on. Excellent! Let's ask Tommy why they lost the 1978 series.

He mentions the obvious downside - there will be "blood in the streets" on those blogs if we have another strike. However, this is great marketing - MLB has just turned every baseball fanatic with a broadband connection into a potential advocate.

Scoble reports that the IE7 team is listening to complaints about CSS problems:

Address CSS consistency problems. Our first and most important goal with our Cascading Style Sheet support is to remove the major inconsistencies so that web developers have a consistent set of functionality on which they can rely. For example, we have already checked in the fixes to the peekaboo and guillotine bugs documented at positioniseverything.net so use of floated elements become more consistent.

That will make our lives simpler, that's for sure...

One of the things I do every day is check the VW Wiki and the Cincom Smalltalk Wiki for spam. On a fairly regular basis, someone hits them with spam. The amusing part is how inept the spammers usually are. Have a look at the history page here - notice how each spam attempt seems to take 3, 4, sometimes 5 or 6 attempts? Not only are these people obnoxious; they're stupid on top of it all

I was wondering what to put together for a screencast this week, and Michael suggested that I take a walk through BottomFeeder. So here it is - the compressed AVI file (201 MB) and the WMV progressive video (36 MB).

Dana VanDen Heuvel points to the BusinessWeek cover story on blogging. Whatever your opinion of corporate blogging is, you are going to get asked about it - it's gone fully mainstream now.

Microsoft has become the old IBM. And I don't mean that in the dominant sense, I mean it in the lethargic, mid 1980's sense. Have a look at the evolve campaign they are using for Office, for instance. In many ways, this has got to be the most insulting campaign I can ever recall seeing. What is MS saying about their current user base? That they are witless dodos, unable to get anything useful done unless they upgrade right now. Just look at the online ad (which is also in this week's PC magazine, right at the front).

The critical guy is in the field, so guess what? No progress - can't possibly move forward. Umm, has MS heard of this new thing called email? I seem to recall collaborating with it as far back as the mid 90's. Is it as good as team tools that can do online linking? No, probably not. On the other hand, if the guy in the field is at a site - hotel or office - with a firewall, what's the liklihood of that firewall allowing Office tool interop outside the LAN? Pretty close to nil, I'd say.

This campaign insults current users, and it's technically illiterate to boot. Looks to me like Scoble has his work cut out for him.

It's a bad idea to outsmart yourself with clever alert messages:

Sysadmin pilot fish gets a wireless-enabled handheld computer with lots of cool features. "I find out how to use a voice recording as the alert tone when I'm paged, and record a message that says, 'Wake up, @#$%!' when I'm paged by the servers," fish reports. "And promptly forget about it. Until I'm in a meeting. And get paged." Red-faced fish can only mumble, "My server is paging me" -- and beat a hasty retreat.

Reminds me of an error message a consultant I worked with once inserted into a general ledger app. He was working late, very frustrated, and had an "account not balanced" error pop a dialog that read "Balance this, a******". That went over well in acceptance testing :)

Cincom's Tom Nies was recently in London, where he was interviewed by the London Times online.

Don Park points out that the end result of "no one pays for anything" is a place we don't really want to arrive at. meanwhile, the RIAA is complicit in this, IMHO - instead of working with new technology and offering a legal path, they want to outlaw progress. Their answer to the futility of that approach is lots of lawsuits. There's a way to make friends and influence people...

In response to the very end of this article, where Rodney Bates said this:

Smalltalk pays a high price elsewhere for taking object orientation to the extreme, notably in complete loss of static typing and serious runtime efficiency penalties. Special, one-instance forms of classes are, for many programming problems, not as good a conceptual match as modules. But at least it provides a single, consistent, and syntactically explicit call mechanism.

I thought I'd ask our lead VM engineer - Eliot Miranda - for some details on method lookup in Smalltalk (VisualWorks in particular):

Rodney, you should read the following books & papers (in order); they'll help you understand Smalltalk's performance.

[Goldberg83] Adele Goldberg, David Robson, Smalltalk-80: The Language and its Implementation, Addison-Wesley, 1983, ISBN 0.201.11371.6.

Now out of print but available by combining

• Adele Goldberg, David Robson, Smalltalk-80: The Language, Addison-Wesley, 1989, 0.201.13688.0
• The Blue Book (Implementation)
• [Deutsch84] L. Peter Deutsch, Allan M. Schiffman, "Efficient Implementation of the Smalltalk-80 System", 11th Annual Symposium on Principles of Programming Languages, pp. 297-302, January 1984, ACM.

Context Management in VisualWorks 5i

Eliot Miranda - Available on the web here(PDF)

But briefly, here's how things are faster than you expect. Message selectors are maintained by the system as a pool of unique strings (Symbols), so that equality comparison of message selectors requires only comparing the addresses of the symbol objects. In the 70's and early 80's message lookup was optimized by the run-time system maintaining a small (1024 or 2048 entry) method lookup cache that remembers recent method lookups. The table is hashed by the identity hash of the receiver's class and the message selector. On early systems the id hash is equivalent to the object's address. Method lookup then becomes:

	hash := receiver class hash + selector hash bitAnd: CacheSize.
	(cache at: hash) class == receiver class
	and: [(cache at: hash) selector selector])
	       ifTrue:
	               [targetMethod := (cache at: hash) method]
	       ifFalse:
	               [targetMethod := self lookup: selector in: receiver class.
	               (cache at: hash)
	                       class: receiver class;
	                       selector: selector;
	                       method: targetMethod.

Since then Dynamic Translation (a.k.a. JIT compilation) has ncreased performance by nearly an order of magnitude. The run-time system does not interpret bytecode; instead it maintains a cache of the most recent used methods compiled on-demand to machine code. We call these nmethods. Every message send is first translated into the following machine code sequence:

       classRegister := selector.  "i.e. load a register with the address of a symbol"
	call unlinkedSend1Args. "i.e. call a run-time routine to find the method, encoding
	                                               the arg count in the call for arg counts 0 to small n"

When unlinkedSend is invoked it locates the receiver from e.g. argument registers, obtains the selector from classregister and uses a modified version of first-level method lookup cache algorithm above to locate an nmethod for the lookup. If an nmethod isn't found it searches the class hierarchy, translates the method to native code and stores it in the first-level lookup cache. And now the clever bit... The send site is rewritten from

	classRegister := selector.
	call unlinkedSend1Args.

to

       classRegister := class. "i.e. whatever the class of the receiver was when unlinkedSend was called"
	call nmethod.entryPoint

The nmethod's code at entry point then checks that the class of the current receiver agrees with that stored in classregister, e.g.

entry:
	tempRegister := receiver class.
	tempRegister != classRegister ifTrue:
	       [self handleSendMiss].
	...

So if the receiver's class is the same as it was when the send site was rewritten the target method is the same and we're done. So we simply have a class dereference, a regiser assignment and a comparison. 90% of send sites are monomorphic. So this speeds things up enormously.

Polymorphic send stes are sped up by using "polymorphc inline caches" or PICs, which look like a jump table, doing a series of class comparisons.

There is also substantial mechanism to allow native stack frames to be used, creatring context objects for method activations only when required.

Smalltalk method lookup is fast

This slashdot story reminds me of something - many - possibly most - of the chips manufactured on the planet are built in plants controlled by VisualWorks Smalltalk. AMD controls their fabs with VisualWorks; so does TI. There's a small firm in Texas, Adventa Control Technology - that sells wafer fab control software to a bunch of hardware vendors - which means that all of those outfits use Smalltalk as well. Bottom line - you may well use Java or C# - but it's very likely that a bunch of the chips in the box you use were produced by Smalltalk.

Another thing too - it's almost certainly the case that the computer you use - if it was shipped long haul at any point - arrived via VisualWorks Smalltalk software as well - the vast majority of long haul container shipping runs on Smalltalk as well.

The latest update on the StS 2005 Coding Contest:

The Smalltalk Industry Council (http://www.stic.org) is pleased to announce the first annual 2005 Smalltalk Solutions Smalltalk Coding Contest. The Smalltalk Solutions Technical Conference will be held in Orlando June 27-29, 2005 and will serve as the home for the coding competition finale. Smalltalk Solutions is the premier forum for bringing together Smalltalk users, developers, vendors, and enthusiasts. FAQ's for the contest can be found here

Coding contest prizes include:

1st round of the competition

The top 3 ranked in no particualr order will receive a free conference registration and a free membership to STIC

2nd Round of the Competition

• 1st Place - $1,000 USD to be used towards a future Camp Smalltalk attendance
• 2nd Place - iPod
• 3rd Place- iPod shuffle

Each of the finalists of the first portion of the contest will receive a Smalltalk Solutions 2005 conference registration valued at $670 USD as well as a complimentary individual membership to the STIC. This does not include travel, lodging meals, tutorials, or any other fees associated with the conference attendance. Please note, in order to compete in the second round of the contest, finalists must be able to attend the conference. The second round of the contest will consist of the three highest ranking contestants who are able to attend the 2005 Smalltalk Solutions conference.

The Smalltalk Solutions Coding Competition is broken into two phases of competition. The first phase begins on Monday, May 16 at 9 a.m. EST and ends on Wednesday, May 18 at 9 a.m. EST running for 48 consecutive hours. Registration will begin March 1 and participants must register for the competition online at www.stic.org by May 13 at 6 p.m. EST. Confirmed registrants will receive the requirements for the first phase online.

All coding must be done in Smalltalk. The problem will require a web application. Client GUIs will not be acceptable solutions.Conference registration is not required to participate in the first phase of the competition. Please note, in order to compete in the second round of the contest, finalists must be able to attend the conference. The second round of the contest will consist of the three highest ranking contestants who are able to attend the 2005 Smalltalk Solutions conference.

One representative from each of the four board member companies consisting of Cincom Systems, GemStone, IBM, and Knowledge Systems Corporation will judge the first phase of the competition. Each submission will be submitted to the judges as blind submissions and a total of three (3) winners will be selected to compete onsite at Smalltalk Solutions 2005 in Orlando, Florida. The winners of the first phase will be announced on June 1, 2005 on the Smalltalk Industry Council web site.

The second and final phase of the competition will take place on Sunday, June 26, 2005 from 6 p.m. to10 p.m. onsite at the Wyndham Orlando during Smalltalk Solutions pre-registration. The details of the second phase of the competition will not be released to the finalists until the competition begins.

Prize winners will be announced during the keynote general session on Wednesday, June 29, 2005.

See you in Orlando!

Here's a tip for this professor: If you have really sensitive information on a notebook - information like this:

You are in possession of data from a hundred million dollar trial, sponsored by the NIH, for which I'm a consultant. This involves some of the largest companies on the planet, the NIH investigates these things through the FBI, they have been notified about this problem.

You are in possession of trade secrets from a Fortune 1000 biotech company, the largest one in the country, which I consult for. The Federal Trade Communication is very interested in this. Federal Marshals are the people who handle that.

This is the kind of data that warrants two things, IMHO: encryption of the data in question, and a hardware level password. This not to excuse the thief; far from it. On the other hand, this professor was every bit as negligent as I would be if I dashed out the door, left the door wide open, and was then stunned to discover that things had been stolen.

I hope the people who entrusted this prof with this kind of data are having second (and third, and fourth) thoughts about doing so in the future. Rest assured, someone engaged in industrial espionage would not be as careless about exposing their position as the naive thief here was.

As most people have heard by now, Comcast has been having DNS problems of late. The upshot of this for me is that I lose network connectivity for brief periods of time just about every day. This is irritating - but it's even more irritating on my Windows notebook. About 50% of the time Windows doesn't reacquire network connectivity after things go back to normal. It can see the router under those circumstances, and my Linux box can see stuff - but there's no DNS resolution on the notebook.

The thing is, I have no idea what this is - Windows, my router, the hardware in the notebook itself? Anyone else see this sort of thing and have any ideas for me?

I wonder if Dave Winer would be as copacetic with a registration of something like AboutDaveWiner.com:

For what it's worth, and seriously, no joke -- I don't think Rogers should give benedictxvi.com to the Vatican. I think the domain should be used for an independently-authored weblog about the policies and actions of the new Pope by someone who is expert in the papacy and independent of the Catholic Church. What an opportunity to get serious visibility for weblogs as a source of news and perspective. Imho, it's not about heaven and hell, eternal damnation or Rogers's grandmother. The church is a hugely powerful political, social and economic force, and its actions are controversial and deserve some visibility, and MSM isn't doing its job. And for the new Pope, it's a chance to participate in history. It's the kind of thing you might imagine his predecessor really going for, until of course it got a story he didn't want them to get. ";->"

Somehow I doubt it...

After yesterday's post on the blog client that ships with BottomFeeder, I thought it might be worthwhile to create a standalone poster. So, I'm in the process of doing that now. Like Bf, it will have the ability to update itself in place. I have some adjustments to make before I can release it that way; mostly a matter of shuffling build directories and scripts. I should have something more to say on this before the weekend.

Steve Rubel pointed out an interesting sounding seminar on corporate blogging in NYC this May. I think I'll attend - the price looks good, and NYC is a fairly short train ride away for me.

Tim Bray has been looking at Blog clients - in particular, cross platform clients. He missed one - the client that ships with BottomFeeder. It's a WYSIWYG XHTML editor (which also allows you to flip over to plain tag mode if you actually like that sort of thing). It works with the MetaWebLog API, the Blogger API, and the MT API (as well the API to the Silt Server, a nice, portable, simple blog server).

There are some issues; the spell checker isn't really working right in the WYSIWYG mode yet, for instance. That'll get addressed soon though. I've tested the client against Blogger, and it works there - I've also tested other clients (like ecto and BlogJet) against my server using the MetaWebLog API, and the BottomFeeder client poster works the same way both those tools do - ditto the MT API.

What's it implemented in? Why, Smalltalk of course - Cincom Smalltalk, to be precise. I found some of Tim's assumptions a bit odd. Take this, for instance:

I don’t know of any other plausible clients that are Java and hence portable, so I think bloged is going to have legs, and is worth us funding some further development. Particularly when the Atom Publishing Protocol becomes ubiquitous. [ed: bloged being a Java client that Gosling and a few others at Sun have tossed together].

When Atom publishing format becomes ubiquitous? Here's the thing - Atom is going to be one format among many (as much as MetaWebLog API sucks). The problem for Atom format is that it's late to the game, and the other solutions - pathetic though they may be - actually work now. I'm sure I'll support Atom with my client eventually - but eventually could be awhile from now. Here's the big thing though - portable doesn't mean it has to be Java. We were doing binary portability in Smalltalk 15 years ago...

Overheard in the Smalltalk IRC channel:

The users I know are so clueless, that if they were dipped in clue musk and dropped in the middle of a pack of horny clues, on clue prom night during clue happy hour, they still couldn't get a clue.

heh.

Update: No, this isn't what I think of users, either of Cincom Smalltalk or of BottomFeeder. I just find that set of words amusing.

I didn't point out that we have a new blogger on the site - Rowan Bunning of Software With Style. Rowan is the product manager for SwS, so subscribe to his feed for the best info on what's up with the SwS product suite.

Torre should worry about Johnson "springing back". Johnson is (or at least, was) a great pitcher - but his knees are about to fall off. The Yankees would be far better off with a shaky 23 year old than with a shaky 40 year old with bum knees. I fully expect Steinbrenner to not get that though, and go looking for another over the hill pitcher. Sigh.

Sci Fi Wire reports on something that always irritates me - pulling a series when there are episodes "in the can":

Fox has again pulled the plug on Tru Calling, taking the supernatural series off the air after the April 21 episode, meaning that viewers who were trying to catch up with the canceled series' last six episodes will miss the final one, TV Guide Online reported.

Look, I understand the whole ratings imperative. At the same time, this kind of thing ticks off a lot of the people that you would like to keep happy. Who am I talking about? People who own and use PVRs (and heck, even people who only have VCRs). Tru Calling has one episode left - so why not air it on a Sunday night at 3 AM? I won't stay up for that, but my ReplayTV will find it. Ditto a show like Firefly or WonderFalls - airing the remaining episodes during slots when no one is watching anyway does no harm to the bottom line, and will yield some amount of positive feelings.

Instead, networks go ahead and do stupid stuff like leaving the last handful of episodes hanging. What's the point?

Anyone who's been paying attention knows that corporate blogging is on the rise. This article points to some stats on that - apparently 45% of the biggest 1000 firms either are blogging now, or plan to do so soon. This is where the miasma of corporate standards is going to run smack into the fresh voice of unhindered blogging.

Should companies be ok with having people say anything on a blog? No, they shouldn't - but on the other hand, there's such a thing as going too far - listen to this so called expert's opinion:

Experts on business blogs say the best safeguards against harmful posts are to institute proactive controls.

"Nothing should make it to the public eye without at least one other set of eyes on it, in any company," said Matthew Oliphant, co-founder of the corporate blogging consulting firm BusinessLogs. "The best way then to run your blog publishing is like any other publishing house: You have post writers and editors, as well as an editor in chief and a publisher. Writers write; editors edit the writing."

Yeah, there's a plan - just treat blog posts like press releases and watch the interest fly in :) For good or ill, you're going to have to use a lighter touch. First off, you should have a policy you can point employees at: Sun has a good one here, for instance. Rather than filter everything upfront, you're really going to have to make judgment calls based on policy. More simply, hire good people and have some trust in them - but make sure to make them aware of the boundaries.

Rok Hrastnik has released a new report - The Business case for RSS. It's a useful summary of his previous work in this area. Here's the direct link to the report.

Today's update brings us to Sam Shuster's Pollock presentation:

Pollock - Now and For The Future

presentation

Shuster, Samuel: Cincom Systems

Monday 2 pm to 3:30 pm

Abstract: In this presentation we will present new widget features that Pollock provides and show how E-Z it is for you to use them in your applications. We will also take a look at how to configure hot keys for your applications as well as presenting an overview of the major refactoring that took place at the start of 2005 to make Pollock even more flexible. The Pollock roadmap to final Production will be discussed as well as VisualWorks GUI plans for the future.

Bio: Samuel S. Shuster is the GUI Lead for VisualWorks. His pride and joy is the Pollock GUI Framework which is slated to replace the current VisualWorks GUI framework over the next few years. When he's not responding to the constant "When Will Pollock Be Done" questions, he sits in the corner of his livingroom, looking dazed.

See you in Orlando!

There's been some grumbling about things at Microsoft - from people at (or recently at) Microsoft itself. Mini-Microsoft is interesting today, and Dare had a good piece up the other day as well. Sounds to me like all is not entirely well in the b0rg cube...

Update: James Governor has some interesting thoughts on all this, with a particular focus on how it might affect Scoble. I've often wondered about some of the bomb throwing Scoble does within MS. Back in the 90's, I spent a fair bit of time at ParcPlace-Digitalk and ObjectShare throwing bombs - some of them public (in USENET - the blogosphere didn't really exist then). One thing I learned was that bomb throwing - especially the public kind - almost never works. It puts your targets on the defensive, and makes it harder for your allies to join with you. You get a lot of private claps on the back, and very little public support.

Are there times I disagree with Cincom management? Sure there are. You won't see me trying to air the dirty laundry here though, because I don't think it would be productive. On your way out of a job, such behavior burns bridges. What do you think it does while you're still on the job?