Thinking About Desktop Eyecandy

An anonymous reader writes "This article ponders over whether excess eye candy and special effects being incorporated on the desktop is a good trend after all? The author explains why he thinks the users are taken for a ride by the OS companies in compelling them to upgrade their hardware in order to enable these processor intensive and memory hungry special effects."

Comments

Disable vs Remove

[TiggertheMad]

...you made a good point, that eye candy is ok, provided that it can be turned off. However, you may not realize that isn't always that simple.

Let's take a hypethetical situation. Lets say I write a UI that uses a 3d api to render the desktop. (we will call this supposed UI, 'SparrowGrass' so we have a name to work with.)

Using 'SparrowGrass' I can enable all sorts of 'spiffy-wa'(as my console gamer friend calls them) hardware accelerated effects, such as dynamic shadows, translucency, and such. But because they are expecting that there is a 3d card with a good T&L chip in the machine, it will run like a dog without it.

So either because I find such 'spiffy-wa' effects morally offensive when I am trying to remotely reconfigure a DC, or because I lack the latest 3d card, I choose to disable the fancy 3d features of 'SparrowGrass'. However, I am still using a 3d API to render the desktop.

If you looks at one very famous company's 3d API, printing text to the screen involves rendering a couple of polygons, and basically texture mapping the text onto them. While you have turned off the 'spiffy-wa' features, you are still going to be taking a hit for using the 3d API in the first place.

it seems unlikely that there will be two sets of .dlls supported, one for providing a 3d based desktop, and another for providing a 2d desktop.