anidais, on 18 August 2012 - 17:12, said:
Because they didn't plan to add a "metro" theme to the desktop until the community asked for it after trying the consumer and release previews. What more proof than the fact they polished the aero interface and made it simpler and even updated the caption buttons and other things? I mean, if they had in mind to get rid of aero since the beginning, why waste resources updating the aero theme and making changes up until the release preview? They could've had the RTM theme in the developer preview or at least in the consumer preview and let people test it.
It seems at the last minute they said "people are asking for a better integration between the start screen and the desktop so let's see what we can do". I am just speculating, but what other reasons could there be? This also explains why the old aero icons are still there. They didn't have time to update those and probably were not planning to change them at all. Again, I am just speculating.
Plausible theory, but one problem: "Aero Lite" coexisted alongside the old Aero in some older leaked builds and probably the previews.
Perhaps they always had the intention to replace Aero, but were too incompetent to do it timely while they plunged resources into the Metro/modern UI.
RandPC, on 18 August 2012 - 18:43, said:
Unless the kernel were to treat operations synchronously, and/or you're incredibly limited on processing power... ie. pre i486 type speeds, the amount of processing time required for playing a small audio clip is infinitesimal. There is no chance whatsoever that it would save them even a half second worth of boot time on even the slowest ARM cores.
It's definitely an aesthetic design choice that boot sounds are disruptive.
Playing sounds isn't an intensive task, but initializing the audio stack and drivers is probably noticeable enough to delay the login process by a small amount.
Also, sometimes the login sound plays a few seconds after the desktop appears on Windows 7 when there's lots of disk I/O.