The Daily Parker

Politics, Weather, Photography, and the Dog

Brrrr rabbits!

Trivia: The last time it was this cold[1] on my commute to work was February 18th.

When cold fronts move across Chicago in November, we get slammed. Saturday's daily maximum at Chicago O'Hare was 18.3°C (66°F), and the daily minimum Monday morning was -2.2°C (28°F). In Chicago, this constitutes a gradual decline.

Yesterday, the heat gave up and went to Miami, leaving us, this morning, shivering our timbers at -13.3°C (8°F), which even I call cold.

At least the sun is out.

Keep your eye on Chicago weather and the the view out Inner Drive's office window to understand my pain.


[1] -9.4°C (15°F); in February it was -11.6°C (11°F).

Build or buy?

About every five years I learn something about my craft. This is an average; the last seismic shift happened in 2002, but the one before it happened in 1995.

It's happening again. This time, I'm learning how my craft gets in the way of my business.

For the past three years (since the last time a two-by-four hit me) I've worked on the Inner Drive Extensible Architecture™, a comprehensive framework on which Inner Drive can build marketable applications. It's a masterpiece, in the way a fine, ornate table would demonstrate the competence of a 17th-century carpenter.

It turns out, I missed the advent of steam.

See, other people have already done it, and they're giving away their code. So over the past few weeks I have slowly come to realize that there is no point continuing this effort in the same way.

This demonstrates a constant, historic tension in business software: Build or Buy. Build something exactly the way you want, or buy something that's close enough.

Open source software, like Das Blog and DotNetNuke, makes this choice even more stark. Can one countenance spending 600 development hours on creating something that has half the features of something anyone can download for free?

More on this later, as I refactor the IDEA to extend, rather than duplicate, the mass of free stuff out there.

Why not a privacy amendment?

Dan Savage's Op-Ed today (reg.req.) asks a reasonable question:

If the Republicans can propose a constitutional amendment banning gay marriage, why can't the Democrats propose a right to privacy amendment? Making this implicit right explicit would forever end the debate about whether there is a right to privacy. And the debate over the bill would force Republicans who opposed it to explain why they don't think Americans deserve a right to privacy - which would alienate not only moderates, but also those libertarian, small-government conservatives who survive only in isolated pockets on the Eastern Seaboard and the American West.

Thanks to Angela Riccetti for this one.

Sony digital rights management goes too far

The Code Project has today publicized details about Sony's DRM CreepyWare that lets Sony know what CDs you're listening to. It also hides in the bowels of your Windows operating system and can't be un-installed without downloading a buggy patch from Sony.

I'm all in favor of protecting copyrights. But this is creepy, and more offensive than the Mickey Mouse Protection Act of 1998.

Update: The L.A. Times has the story now.

Ich werde The Blog ersetzen

Translation: I am going to replace Das Blog.

Yes, as much as I like it—and I do, despite my gripes—I've found something more in line with the way that I work: Community Server. I've downloaded both the current version and the new Beta, and as soon as I have time (tomorrow at the earliest, Saturday at the latest), I'll switch over.

Since this is a brand-new blog, I have little compunction about wiping out all the permalinks. (There are fewer than 10 at the moment.) We apologize for the inconvenience.

Quick poll

Which do people prefer: having all the entries on the front page, one line per entry (like they are now), or having the complete posts all in a column? Talking Points Memo is an example of the "flow" design.

(I also still don't have the comment problem resolved, so please email me with your thoughts.)

Thanks for your help.

Moving this to ASP.NET 2.0 is hard

I have to give up on converting dasBlog to .NET 2.0 for now. The ASP.NET model has changed significantly from 1.1 to 2.0, breaking every single page in the application. In other words, many of the techniques developers used for making pages do interesting things in 1.1 simply don't work in 2.0, because the system doesn't work the same way. I may have missed something simple—but I don't think so at the moment.

So I think all of the pages in the application need to be changed in order to make it work. In fact, I think the whole application needs to change, to take advantage of the new features in ASP.NET 2.0. I figure fixing the current pages will take about 8-12 hours, which I can't spare until Thanksgiving. I'll just have to live with a few annoyances for now. Redesigning the application isn't going to happen.

Tuesday I'll take a look at it in Visual Studio 2003, so I can at least see how it works step-by-step, and possibly see if some of these annoyances will take a lot of time to fix.

The glimmer of light in all this is that only the Web application needs to change. All of the supporting assemblies compile without any major problems. So instead of changing hundreds of classes, I think I only have to change a few dozen.