On Friday my team was mixing in post-code freeze decompression. One of our developers was explaining a WinXP configuration setting vis-a-vis Control Panel. Of course there was the extra step of switching to classic mode - and simultaneously everyone wished a collective: "get out of my way." The principle was that even medium-versed users of Windows XX products are often forced to take an unnecessary step or two in their use of the product(s).

And then I read this:

This one came up on the FlexWiki mailing list the other day. I should have known it, but I missed it, and it's worth spreading around.

A user complained that their FlexWiki install would periodically respond very slowly. The wiki was under very light load, so it didn't seem like a traffic problem. I was initially a bit confused, because the user reported that they hadn't changed the <processModel> element. Changing <processModel> to recycle the ASP.NET worker process periodically would have explained the problem, but the default is not to do that.

At that point,·Michael Teper·pointed out what I should have remembered: under IIS6, <processModel> is ignored in favor of the IIS6 metabase settings. If you go into the Internet Services Manager and pull up properties for an application pool, you'll see right there that by default, IIS will recycle the worker process every 29 hours (yes, 29), and after 20 minutes of inactivity. So on a lightly-loaded server, you're going to see a lot of recycling, and the consequent periodic delays. If you're supporting an internal web server that doesn't get hit that often, changing this value might be a good idea.

[Via CraigBlog]

...so even though anyone reading this blog or that blog knows better; it still amazes me that settings in IIS - and most elements of the MS stack - default to a time-consuming setting rather than a time-saving setting. Until that trend is corrected - in security, OS services, and business services - the word on the street for these products will be: default for dummies.