:: Re: [Dng] Readiness notification
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Jonathan Wilkes
日付:  
To: dng
題目: Re: [Dng] Readiness notification
On 06/13/2015 09:34 AM, Klaus Hartnegg wrote:
> Am 13.06.2015 um 13:33 schrieb Laurent Bercot:
>> 30 seconds is a lot. What if you could get your desktop ready in
>> 5 seconds or less ?
>
> This would mean less than what most people think. Because everything
> longer than half a second is perceived as being forced to wait. As
> long as an improvement stays above this threshold, it just replaces
> one forced wait with another forced wait.


I had some problem awhile back that required making changes in the Grub
menu to see the result after bootup.

10 reboots * 5 seconds = 50 seconds
10 reboots * 30 seconds = 5 minutes
5 minutes / 5-second-reboots = 60 reboots
5 minutes / 30-second-reboots = 10 reboots

It's not just a matter of speed, but also granularity. Yes, the faster
boot time would give 6 reboots in the time of 1 on the slow machine.
But it also lets me bail on a particular course of action sooner. Where
I'd be sitting at the slow machine twiddling my thumbs for another 25
seconds, on the fast machine I'm analysing the feedback and choosing a
new course of action. Given the average human attention span is only
about 20 minutes, this is a qualitative difference.

I mentioned Grub because it's the first that popped into my head. But
given another 50 seconds I'd also mention the following:
having the (practical) option to restart on a system freeze if you're in
a hurry
testing out the rt kernel vs stock kernel
having the option to restart in a presentation if you get stuck somehow
(or if the projector somehow only gets triggered at bootup)
dev'ing rt kernel, init system, and lots of other stuff that requires reboot

-Jonathan