Re: vista vs XP
Fog Tanner
>My first choice is still Linux. But when I have to use Windowz, my first choice is 98SE followed by Win2K. Everything after Win2K is just bloatware and getting worse. All this is being done is the same old core OS is getting wrapped with a new GUI and some more widgetst hat you don't really need.
I am in the software business and know what typically happens. You have an app like Office (or Windowz). It has a basic core processing "engine" that does all the work. The GUI is the user interface to the engine, taking what you enter - reformatting it and passing it to the engine. The engine does its work and the GUI reformats the results and presents them. Next version, same basic processing engine with new GUI for new look and feel. You learn new GUI, enter same data you did before - new GUI has a bit more code for new look and feel, so it may not reformat what you entered exactly right for the engine. Engine gets data, does what it is asked and passes results back to GUI for display. Not what you expected, so a problem is opened.
Problem is looked at, found to be a problem in GUI. If a simple fix and there is more that a few reported then a fix is generated. If it is not simple or there are only a few, then it is fixed in "next release". Next release will pick up some (but not all) of previous release problems for fixes. But, since the GUI is being redesigned for new look and feel that problem may or may not be fixed.
Meanwhile back at the ranch, you are still using the software to do the same thing you did five years ago and have not used any of the new widgets that have been added. You are only getting incorrect results from what you did five years ago. Each year a new release comes out and you are told that you need it - for a price. Most of the time they are really bug fixes for what should have been fixed as part of the original purchase five years ago.
If your apps and hardware ran yesterday and they are running today, they will run tomorrow. Software does not go "bad" or spoil, marketing creates the need for change. Most of your insurance policy processing is being done by applications written in the 1970's-1980's (and there are some much older than than that). There is an adage in hot rodding, "if it aint't broke, don't fix it".