Re: Really!?
There is a finite amount of programmer effort assigned to the Terminal project. Do you want some of that effort:
A) Spent writing fancy settings-update code so that all the old settings get upgraded automatically, in a clearly labelled pre-release version where people using it have been warned there may be breakage, OR
B) Spent actually implementing new features or fixing bugs?
Most people would say B.
(And for the record, it's *not* fixable in the install script, because Windows is multi-user and networked. So you have to cope with a program being installed while user X is logged into a completely different PC, then later user X logs in and his/her user profile is copied from the fileserver to the local PC, then user X runs the new version of Terminal. So the settings upgrade code would have to be part of the Terminal application, and run as one of the first things the Terminal application does when you launch it).
Biting the hand that feeds IT
