Smalltalk Tidbits, Industry Rants

I decided to put together a new dev build - Holger has been making some enhancements to Twoflower - he's enabled text copy from within Twoflower (which means you can copy text from the HTML View now!). This makes it far more useful, and it's a feature that ought to be out for testing. The dev build is uploading now. The panic? Well, I had completed the image build, and turned to using ResHacker to package up a Windows exe. Imagine my panic when it just didn't work after having updated to XP! After some wailing and gnashing of teeth, I used Google to track down a newer release of ResHacker. I finally located one here. After downloading it, i was able to finish the build. If you want to see what Holger's been up to, give it a whirl!

A few days ago, I posted this, in response to this post. It was actually a general frustration on my part, and not a rock hurled at the poster. It has now received this response, and I do have some issues with that:

The weakness of both Lisp and Smalltalk (and many other cool researchy languages), is that neither have ever been that good at talking to the machine, which makes them pretty much useless for real work. Today, we have lots of "managed" languages that can talk to system pretty well. Java can do that, and the various languages atop the .NET CLR can do that. And from an industrial perspective that's important. I'm oversimplifying a bit here, but that's been the reality / perception at various points in history over the last 20 years. From where I sit, it looks like the best we can hope to do is to get an advanced language which can use the CLR's ability to talk to the machine. And the CLR that it talks to ought to be the ECMA / Mono one, not the Microsoft one. That would get you a decent language, portability across hardware / os at a binary level, and the ability to talk to the hardware in a rich fashion.

huh? Useless for real work? Where in the heck does that come from? Most applications, in simplified form, look like this:

1. Grab Data from Database
2. Present Data for user to view/modify/create
3. Push any modified data back into the database

Boil it down, and that's what most apps are. Not number crunching, not games in need of the fastest hardware/software (although, Lisp and Smalltalk have been and are being used in games). To me, this sounds an awful lot like the general industry problem of premature optimization - developers the world over are obsessed with making things faster - never stopping to ask if it's the real problem. In most cases, it's not. And managed code is a good thing - having access to pointers is a necessary evil for some levels of work, but for the vast majority of applications, they are a useless distraction - in reality, little more than an error generator. I've done just fine without pointers for a decade, and will do just fine for another decade without them. I wasn't the only one to have this thought; Chris Double weighs in as well:

Maybe I'm misunderstanding Ted but I don't agree with this statement. Perhaps it was true in the past but modern Lisps and Smalltalks seem to have no problems talking to the machine. Dolphin Smalltalk applications look and feel exactly like normal Windows applications. And that's because they are. It's also very easy to call API functions. Corman Lisp, a Common Lisp system for Win32, also has very good methods of talking to the machine. You can practically paste in a C header file definition for the API and Corman Lisp will generate the necessary Lisp code. You can create DLL's in lisp that are callable by C programs. You can even code in-line assembler if you really want to get down and dirty.

Now, VisualWorks doesn't (yet) have the capabilities that the Chris mentions above. But it does pretty well, and the VW VM will be available as a DLL for 7.1 - which means that you'll be able to deploy VisualWorks apps as DLL's at that point. This blog is Smalltalk powered, and the BottomFeeder application I spotted these posts with is a client application that integrates pretty nicely with Windows via the registry. I don't get it....

This report, which I discovered here is an eye opener. Kind of takes me back to my days (1960's) in elementary school, with the "duck and cover" drills. Definitely a more coffee kind of read....

I've said more than once that static - or manifest - typing just gets in the way, and causes more problems than it solves. A lot of people are starting to catch this drift with the rise of Agile methods and test-first. The MS folks obviously don't - here's an interesting example:

What I really want for this class is to serialize it both directions - I want the object to be serialized up to the server so the server can play with it, but when AddItemToBag returns I want the modified bag to come back down to the client. I was all geared up to start exploring custom marshaling when I tried one simple thing - I changed AddItemToBag to take a ref IIntBag instead of just a plain IIntBag:

 public void AddItemToBag(ref IIntBag bag)
 {
  Console.WriteLine("bag[[\"1"] = 1;");
  bag[["3"] = bag[["1"] + bag[["2"];
 }

This turned out to be exactly the combination I wanted - the hashtable is serialized in both directions! Reasonably obvious I suppose but I wasn't convinced it was going to work this way. I figured "ref Int" wouldn't send results back down unless I literally allocated a new hashtable and assigned it to bag. This is too cool. Interestingly the C# compiler demonstrates a little quirk (maybe it demonstrates my own quirkiness) when I try to call the function. If I say this:

IntBagImpl i =  new IntBagImpl();
Server.Add(ref i);

the compiler complains: error CS1503: Argument '1': cannot convert from 'ref IntBagImpl' to 'ref IIntBag' Well, duh. Just for fun I tried this: IntBagImpl i = new IntBagImpl(); Server.Add(ref (i as IIntBag)); Sick stuff to be sure, but hey - it might work :) Alas, the compiler slaps me down with this: error CS1510: A ref or out argument must be an lvalue Changing the type of i to IIntBag of course fixed it, but apparently the compiler doesn't like taking a ref on a temporary object :). Interesting. I wonder what the Mono compiler does here...

that's an example of knowing how to solve a problem but having the type system stand athwart your code shouting stop! Now imagine if he was using Smalltalk - all that time spent fighting the type system would have instead been spent doing something of value

Here's an interesting paper on SWT usage:

When programming in a GUI operating system, you allocate operating system resources for widgets, images, fonts, and other graphical objects. Since there is a platform limit on the amount of resources you can allocate, you must be careful to free any objects that you allocate in your application. If you allocate a resource and do not free it when you are done with it, your application is "leaking" resources. An application that repeatedly leaks resources will eventually consume all of the available resources, forcing the user to reboot the operating system. Fortunately, SWT makes resource allocation and disposal a straightforward process. There are only two rules that you need to remember when allocating and freeing SWT resource-based objects: Rule 1: If you created it, you dispose it. Rule 2: Disposing the parent disposes the children

Ok, that seems like a huge step backwards to me. It gets more interesting:

This is a simple rule. SWT makes it easy for you to remember when operating system resources are allocated; all SWT resource-based objects (like Color, Cursor, Display, Font, GC, Image, Printer, Region, Widget and subclasses) allocate any needed operating system resources in their constructor. There are no exceptions to this rule. There are no methods in SWT (other than constructors) that allocate operating system resources that the programmer must manage. If you didn't call the constructor, then you don't need to free the resources, so don't call dispose on the object. For example, in the following line of code, an operating system font is allocated:

    Font font = new Font (display, "Courier", 10, SWT.NORMAL); 

Since you called the Font constructor to create the resource, you must dispose the font when you are finished with it, as follows:

    font.dispose();

In the following line of code, however, a constructor is not called:

    Font font = control.getFont ();

Therefore, you must not call dispose. The font variable does contain an operating system font resource, but you did not allocate it. If you were to dispose of this font, you would be leaving the control without a font! The results are undefined. So, if you are using any getter that returns an SWT resource-based object that you did not allocate, do not dispose the object.

I suppose developers would internalize (most) of that - but that introduces some nice opportunities for memory leaks and - whatever happens if you call dispose() inappropriately. This is progress? Interestingly enough, this isn't just me as a Smalltalker being smug. I found this here, on a Java developer's blog. Some of his comments:

cbeust on SWT and memory management:

However, I have to agree with Danno about resource handling: the fact that SWT forces you to free manually the resources you allocate is a huge step backward that is going to become a big liability for this toolkit in the near future.

Back to future gang! Looks like the memory leak business will be alive and well in Java land....

We have made the Cincom Smalltalk Wiki with an apache rewrite rule - instead of http://www.cincomsmalltalk.com:8080/CincomSmalltalkWiki, you can now use http://www.cincomsmalltalk.com/CincomSmalltalkWiki. This should make it more accessible to users who can only browse via port 80. There may be some lingering issues - any pages with a "/" in the title will not be visible this way. As they get found/reported to me, I'll fix them.

We had over 2000 downloads of Cincom Smalltalk non-commercial last month, and we have almost 500 so far this month. Interest in Smalltalk seems to be increasing!

I saw this announcement - the 1.0 version of NetNewsWire is getting released at a price of $29.95. The interface looks nearly identical to the BottomFeeder one. They support blogging tools in the for-sale version, and I haven't gotten around to doing the Blogger API yet - although that is coming. They run on Mac OS/X, and we run on loads of platforms - not to mention that BottomFeeder is free and open source. As well, I bet they have more than two people working in their spare time ;-)

My favorite TV night, Tuesday. Both Buffy and 24 are on, and both were very good again. 24 especially - it had me on the edge of my seat the entire time. The story line connecting the elements working against the President (Palmer) and the terrorists (Ali) look to be converging. They've done a great job of relentlessness so far. I'd be looking forward to Angel tomorrow, but my local WB station insists on showing ACC basketball. As if I care about that....

I had a problem the other day packaging a BottomFeeder build with ResHacker. It had been working fine under Windows ME, but did not seem to work after I upgraded to XP Pro. I got things going by grabbing a newer release of ResHacker. Now I get word from Anthony Lander that the version on the CST CD works fine in XP if you first delete the executable file that will be created when you use it. So either download the newer version - I found it here, or delete any old executables before you use the old version.

I finally discovered how some people thought they were getting registered, but had not, in fact gotten registered. The Registration process is a two step thing - first you register, and get sent an email. Then you login, and get sent to the download page. The problem was on that login page - some people apparently hit the "I forgot my Password" button by mistake, and the application was not dealing with that properly - it was simply sending an email, without ever checkking to see whether the user in question was activated or not. That's now handled - such inadvertant mistakes will now be far more gracefully handled. I apologize for the confusion...

Gordon Weakliem has an excellent post on software development up today. He links to Jon Udell, who makes the assertion that "the film industry's project-oriented, just-in-time assembly of resources and talent":

This is really interesting because I was talking to a friend who is both a software engineer and an amateur filmmaker, and he was drawing paralells to software and filmmaking; for example, a filmmaker shoots a lot of film, but doesn't really know how things are going to turn out until the editing process. Which is a lot like software, where it's even more difficult to see where you're going until you get to integration. What's funny is that last night, we were talking to a mutual friend who's a project manager for a construction company. He described his job as "protecting his boss' money", in that the builders will come up with a proposal for how to complete part of a project, and he's the guy who tells them to come up with a cheaper solution. My filmmaker friend exclaimed, "you're the producer!", as in a film producer, who's supposed to rein in the director and the people involved in actually making the film. So I had the realization that the construction industry works this way as well: a builder or developer generally doesn't build anything, they hire people to build it for them. So somebody gets the job of contracting and scheduling the work of concrete workers, drywallers, plumbers, electricians, painters, etc.

That's a great analogy, IMHO. Gordon makes a number of other good points as well, relating all of this to the industry's "standardization" trends - J2EE yesterday, .NET today, gosh knows what tomorrow. Go read his whole post - I'm not going to be able improve on what he has to say.

This is just funny. Linux Today quotes Sun's CEO:

"Industry analysts and others who suggest otherwise are plain wrong", Sun CEO Scott McNealy said at a news conference in San Francisco yesterday at which the company unveiled a flurry of new products and services. "They just don't get it. That's all right, they haven't for 21 years," McNealy said. "Right now, HP and IBM are reading the analyst reports and saying Linux is going to happen and they're abandoning their Unix customers..."

Hmm. I guess McNealy didn't notice this. And speaking of not getting it, there's the entire Java language - a prime example of utterly ignoring the prior art in Smalltalk and Lisp, and shoving out a half baked implementation. Not to mention that in doing so, they handed large checks to IBM and commoditized their entire product line. There's someone that doesn't get it, alright. McNealy needs a mirror.

If you use VisualWorks, run - don't walk - to the public store and load the RBCodeHighlighting package. It is configurable via the system settings, and does the coloring/highlighting as you type. Highly recommended. Kudos to John Brant, Anthony Boris, and Holger for collaborating on this!

So yesterday I posted some on the tense 24 episode and the latest Buffy offering. This yielded this message from an Australian associate:

And on a different but vitally important note - please be very very careful not to give away any plot for 24, Buffy and Angel on your blog. They have only just started running the new series of each in Australia this week so we are somewhat behind.

Heh. I'll do my best.

The rush towards Web Services is interesting. Here's a brand new, text (text!!) based RPC mechanism that is being touted as the interoperability miracle. Wasn't that CORBA once? Yes, there's one big thing that Web Services has that CORBA does not - UDDI, a lookup service. In theory, one can query for existing services in a public registry, and then go use one. That's the theory However, the reality is just a trifle different. Let's take a really simple example - RSS. There are thousands of blogs out there (as well as news sites, etc) syndicating their content via RSS. You would think that this would be a natural for UDDI and SOAP - register yourself as an RSS feed with a registry, along with some keywords on the type of content you provide. Voila, easy to find. Go ahead and do a SOAP query for RSS Feeds - BottomFeeder implements one. Exactly three feeds come back, all from Microsoft. Now go to Syndic8.com - there are tons of feeds there, available directly or via OCS or OPML. This is just an example - here's a widely used service, and one where you would think that UDDI and SOAP would be highly useful - but no one is using it. Heck, these technologies are highly attunded with the Blogosphere, and the API of choice for using Blogs is the Blogger API, an XML-RPC thing. Sound and Fury, signifying nothing? Perhaps. The good part for Smalltalk is that Web Services are (relatively) easy to support. VW, VA, and Dolphin all have support, so the level of "buzzword compliance" is high. Is it more than buzzwords though? So far, no.

Brian Livingston's InfoWorld column is just wild:

Users' ability to remotely use applications through the browser gets creamed, however, if they happen to install Service Pack 1 for Windows XP or various patches for IE 5.0 and 6.0. Breaking this ability was intentional. Microsoft designed the new patches to disable ActiveX controls that have security holes. Unpatched versions allow a malicious person to gain control of a PC when it views a specially crafted Web page or e-mail message. This is all described by Microsoft at http://support.microsoft.com/?kbid=328002. In a related document, Microsoft explains how to restore remote access to users (see http://support.microsoft.com/?kbid=327521). First, the company's terminal server must be updated with new software. Then, the relevant .asp files are edited to refer to a new class ID and file: CLASSID="CLSID:9059f30f-4eb1-4bd2-9fdc-36f43a218f4a" CODEBASE="msrdp.cab#version=5,1,2600,1095" Unfortunately, Tierney says, this change makes it impossible for users to print to a local printer, which is usually connected to their LPT1 port. The problem must be fixed by further of your affected .asp or .htm files. For example, you need to add a line to each file to re-enable printer redirection. Other commands also must be invoked to re-establish drive redirection under Windows XP

Wow. Wow. Applying a patch can leave you broken in ways you'll barely understand unless you read all the relevant files carefully. Simply amazing

Awhile back, I opined that a DC area blog meetup might be interesting. It turns out that there's a blog meetup clearing house. The next DC area meeting is February 19:

The Bloggers have spoken... The Weblogger Meetup in Washington, DC will be:

Wednesday, Feb 19 @ 7PM Dave & Busters White Flint Mall, Wisconsin Ave Bethesda, MD 20895 301-230-5151

Interesting. And email I've gotten indicates that the PBS' Lehrer will be covering this meetup.

It's funny living here after having grown up in New York; the ability to deal with snow and get schools open is so different. In that vein, two things struck me recently: the weather channel is predicting more snow Sunday into Monday, and the school year here has already been extended a week. My daughter is not happy about that. In fact, she's now asking my wife to stop every time she sings "Let it Snow".....

I've been migrating BottomFeeder to VisualWorks 7.1, which is due to be released at the end of March. I've run into some kind of RuntimePackager issue. Once I work through that, a new build will be posted.

From Alan Knight:

Smalltalk Solutions is a primary venue for Smalltalk professionals, regardless of dialect, to meet and exchange ideas. This year's conference is taking place in Toronto, Canada, July 14-16 2003. The program committee is

Vassili Bykov - Cincom Systems Eric Clayberg - Instantiations Steve Cline - Knowledge Systems Alan Knight - Cincom Systems

Presentations involving Smalltalk technology, are requested in the areas of

1. Tutorials
2. Experience Reports
3. Technology Demonstrations
4. Technical Presentations

The focus areas of this year's conference are business issues and internet applications. Presentations on these areas are particularly of interest, but submissions need not be limited to these topics. Presenters receive a free conference registration (one per presentation). Tutorial speakers will also receive a small stipend. To submit a proposal, please go to http://www.smalltalksolutions.com/participate/participate.htm Proposals should be received by March 15, 2003.

Go ahead, volunteer!!

I've moved BottomFeeder to VisualWorks 7.1. This allowed me to get rid of most of the extensions and overrides, and also enabled a more responsive application. The tree view in 7.1 is far better, and we have enabled the +/- controls for it. The latest DEV build is a 7.1 build.

The weather channel is now telling us to expect a pretty hefty amount of snow. i just shopped two days ago, so I'm in no mood to head down to the Giant - it will be packed with the "bread and toilet paper" crowd - whenever snow predictions come for Maryland, it seems that everyone is convinced that this is it - the snow storm that will leave them housebound for weeks. So I was looking forward to not going, but it seems that my wife - a native Marylander - has succumbed to the local affliction. So off I go to brave the crowds....

There is a new version of the Pongo IM client available as a BottomFeeder plugin. Anthony has been doing quite a bit of work, and addressed some bugs. Pull down the Plugins--Available Plugins menu and download it now!

If you browse the BottomFeeder Help or the Twoflower Help - you'll see that both have been updated. Kudos to Rich Demers for the excellent doc!

hat tip to David Buck for the tip about DEVX:

New S# Language Adds Capabilities for .NET Developers In an interview with David Simmons, CTO of SmallScript Corp., we learned about a new .NET language about to debut, the ins and outs of its gestation, as well as some insider history behind the creation of the .NET platform. ... Think way back-back in the ur-ages of OOP development-and one language probably comes to mind before any other: Smalltalk. Even though it was one of the world's first true object-oriented programming systems, Smalltalk's technical underpinnings have survived to the present, and you can see its influence in the object models of both Java and .NET. For example, Smalltalk introduced the idea that all data types in a programming environment are objects, including even base scalar data types, such as Integers and Strings. In an exclusive interview with DevX Wednesday in San Francisco, David Simmons, SmallScript Corp.'s Chief Technology Officer, chief architect of S#, and a seminal force in the Smalltalk community, related the story of the ups and downs of Smalltalk in the 90s as well as the creation of S#. He has been building commercial Smalltalk implementations since 1981.

Always good to see mainstream notice of Smalltalk!

slashdot is reporting on a Cringely opinion piece. The upshot of Cringely's piece - Sun is doomed:

Even Java is becoming superfluous. Java is the Dan Marino of software. Just as the former Dolphins quarterback, Java affected the world so much that history cannot be written without its mention. But nonetheless, neither Java nor Dan ever won the big one. So here is the prognosis. Sun lost $2 billion last year and will probably lose another $2 billion this year. At that rate, the company has at most five years to live. They have just renewed a commitment to the Solaris operating system, which is no longer really viable from an economic standpoint. I know, I know, Solaris users love Solaris, but they don't love Solaris prices. And with a falling market share, Sun can't afford to make Solaris any cheaper. Sun is having the same problem in hardware where their SPARC architecture is falling behind, and -- worse still -- has lost nearly all of its manufacturing support in Japan. Both Solaris and SPARC will absorb vast sums in the coming years and yield absolutely no increase in Sun's market share as a result.

There's more in the piece, but those posted losses are the interesting part. No company can sustain those sorts of losses for long, and if that trend continues, I give Sun a lot less than 5 years. The interesting part will be th expression on the faces of all the Java true believers when they realize that the JCP is merely a nicety - and that Sun falling will make for changes in the Java world. Even if it gets Open Sourced - hello, code forks.

There's an interesting article over on the O'Reilly net, making some points about comment sections and websites:

There's a very interesting trend happening in the arena of micro-publishing. And it's one that, I believe, is connected to the idea of Communities taking place at < 150 people: the death of the 'Comments' section on websites. People don't like to make comments on websites like they used to. Instead they make comments on their own website where they have a voice. I'm not going to tell you that blogging is a new phenomenom (no kidding?!). But what is new is that people aren't just using them for their own original publishing, but are replacing the beloved 'comments section' of popular websites. Think of it this way. Let's say that there is a really interesting story on Slashdot about a subject close to your heart. You wish to contribute to the conversation taking place, but have not commented in the first 200-300 comments. You're voice is generally lost among those already written. Not a terrible thing, but just the way it is. Who is heard among a mob? (I use slashdot only as an example of a mob. Webloggers are out scooping slashdot on a regular basis.)

Slashdot is a great example of this. So many people read and comment that it's hard to keep up, and hard to tell whether any comment you make was heard at all. One of the nice things about running a web log is that you get your own megaphone. Sure, it's smaller - My readership counts in the hundreds (daily), not the thousands. But any comment I make here has a decent chance of generating a comment and/or an email - i.e., a conversation. Any comment I make on slashdot is simply lost in the haze. I'm sure that the same thing happens with the larger and more popular blogs - in the political realm, Instapundit doesn't have comments at all, and Little Green Footballs often has comments numbering in the hundreds on individual posts. In the technical realm, Sam Ruby has a wide enough readership that he started a comment RSS feed - and it tends to be large. What I notice in my own reading is that as the number of items in a feed (or comment thread, etc) grows, the liklihood of my doing a 'mark all read' action increases. There are only so many hours in the day....

Here's another .NET notice of Smalltalk.

Picked up a Smalltalk book the other day, I do intend to learn Smalltalk so that I can research its use in .NET and see what changes it has in its OOP support. I have heard great things about Smalltalk so this going to be one heck of a journey :)

This relates to this post from earlier today. Looks like Smalltalk is getting more notice from the .NET crowd!

Today I added support for the Google Web Services search API to BottomFeeder. So now you can execute Google searches without leaving the tool.

Chris Double is looking for a Linux news aggregator. Well, all he needs to do is browse here.

I added two new BottomFeeder features after nearly killing myself on a toboggan earlier - I don't think my daughter's knee did a whole lot of good when it landed in my ear... Anyway, I added two new things:

• A Google Search interface. The Search Tool now has Google as a search option
• IE Favorites Import - You can import IE FaVorites into BottomFeeder. This is a Windows specific feauture.

Both were pretty easy. Next up, a general re-factoring of the bloated RSSFeedViewer class....

whether BottomFeeder can use the same data files across platforms. Mostly, yes. The btfSettings.ini file actually stores directory separators - soomething I need to fix. The actual data files themselves are easily shared - and in fact, that was the point of the FTP save/restore feature. Since I'm looking at 3 feet of possible snow today, I probably have time to address this issue....

Chris Double asks:

Look at all the platforms that BottomFeeder, an RSS Aggregator, supports. You'd be hard pressed to get that sort of portability with Java even. Cincom Smalltalk seems to be very portable. I'm assuming there is no platform specific code in there?

There's no code that forces platform specific versions. There are some additional features on Windows - using the registry, it's possible to use an existing browser to launch an URL, whereas on other platforms, I have no idea how to do that. We just launch a new browser on other platforms. But there's nothing that ties an existing image to a platform - the image is portable.

Everyone else has commented on the news that Google bought Pyra, makers of Blogger - so I may as well add my two cents as well. Looks to me like validation of a market.

Take a look at the snow hitting the east coast. We've had more than a foot so far, and it's still coming down - the local forecasts are telling us that it will get heavier later. I took some shots with my webcam - if I had a digital camera, I could do a lot better:

Yes, that's my car over there. The side facing the yard is completely packed in - gosh only knows how I'll get in the car when I finally get a chance to get out.

Those are my neighbors. Having the snow blower has made me very popular this winter ;-)

Another shot of my car

I've decided to change the way I deliver BottomFeeder. Up to this point, I've been delivering monolithic builds with the application and the runtime packaged together. What I've been working on today (in between snow clearing) has been a new packaging scheme. When the 2.8 release comes out, you'll see this:

• Tar gzip file for each platform. These will contain the directory structure, the base Smalltalk runtime, and the VM, along with the application. The application will be shipped as a parcel which loads at startup.
• Updgrading to a DEV build or a new version will be as simple as downloading the parcel - the only time I expect to be shipping a new runtime and VM is on new releases of the base VisualWorks product

It turns out that the base BottomFeeder parcel is a little over 400k - and just over 100k compressed. Once I transition to this form of deployment, it should be a whole lot easier and faster to upgrade. I was motivated to do this by reading this critique of BottomFeeder, by the author of the Syndirella aggregator. Some of the criticisms are valid; I've eliminated most of the confusing save/restore options, and moving to the loadable application deployment is another good step. Some of his points are just odd though - he makes a statement that we use screen turf badly. Now mind you, I'm not going to claim to be a GUI layout whiz (That would be Vassili Bykov). However, the screen shots for Syndirella show a virtually identical layout. As to support for Cyrillic - yeah, we don't provide that. If someone provides me with a Russian Locale, I could look into it though. Anyway, I think I've improved the app based on some of those critiques. As soon as I can get the Runtime Packager stability in 7.1 that I had in 7, I'll release 2.8

It snowed all night and into the morning here (with about 1/2 inch worth of ice in there for fun). I spent a good long time clearing that this morning - it was hard even with the snow blower. The plow came by (which baffled me - we live on a street with no outlet, I95 has one lane open, and my street gets plowed. Go figure), and that made it harder - I had a drift about 3 feet high to deal with. That had to be chopped down before the blower could even go after it. To give you some idea of how much snow we got, here are some more pictures:

	My daughter gets started on a snow fort
	My neighbor's kids building a fort
	My daughter and the neighbor contemplate the job in front of them. Meanwhile, I'm stuck on a conference call....

Yes, we are pathetic here in Maryland. Schools are closed tomorrow, as are the local (and federal) governments. Word is that side streets won't be plowed for 1 or two days. At least the power stayed on. In the meantime, I posted the new DEV builds for BottomFeeder. Over the next few weeks I will likely be building new runtimes fairly often (VW 7.1 is still under development). However - once VW 7.1 ships, the runtime should stabilize, and updates will mean just a download of the application parcels. In this case, that's BottomFeeder and Twoflower, and compressed, that's less than 250k.

Yes campers, it's snowing again! The forecast says it's just a tail end dusting - I'm crossing my fingers. Meanwhile, no sign of the 51 inch TV we bought last week. It was supposed to be delivered today - but that kind of assumes roads you can drive on....

Yesterday, I posted on the new deployment process. I'm uploading the first attempt at that now. I re-arranged the download pages as well - DEV builds have their own page now. There will be some shaking out of this over the next few weeks - for one thing, VW 7.1 hasn't shipped yet, and we are now based on VW 7.1. That should stabilize within a few weeks, as we get closer to the VW release date.

Here's one I see in the news every so often - the impending outage of phone numbers. The culprit used to be fax machines, then cell phones. Now, it's VOIP:

Someday soon North American telephone numbers might add up to 12 digits, including area code, instead of the current 10. Verizon, Qwest and BellSouth have urged the Industry Numbering Commission, which regulates the distribution of telephone numbers in North America, to "be proactive" about what the phone companies see as the newest threat to the dwindling supply of available phone numbers: voiceover Internet protocol, or VoIP.

I'm sure that phone numbers will run out eventually. The problem with the frequent alarms is the very real "little boy who cried wolf" problem. Yell about every time a new trend comes along, and no one will pay any attention at all...

Schools are out again tomorrow, as Maryland struggles to get the snow off the roads. The snow fort my daughter has been building made some more progress - and I rearranged the BottomFeeder UI. If you downloaded the new 2.8 dev build, then all you need to do is grab the parcel files I uploaded.

Buffy and 24 were on a roll again. 24 especially - it's reminding me of how I felt the first time I saw Terminator - it just keeps coming at you, head on, no stop. Barely time for air. i'd go into details, but I've been asked not to. Suffice to say, another good Tuesday of TV