61–70 of 110 posts
Earlier quoted context omitted.
The problem with a desktop is that most people have at least one and mostly several applications running. Those need maybe saving as well, before quitting. The mobile phones are better in that way: all apps are required to save their state at any time. So rebooting can be a mindless procedure.
You made me suddenly aware of the fact that I do not actually know how other people use their phones.
1 seconds seems a rather arbitrary measure. In HCI 100ms seems to be the value that's generally taken under which an action seems to be happening instantaneously [1] It's quite sad to see how we hardly use the computing power offered by our modern computers to actually speed up common tasks, but instead bloat it up with all kinds of stuff. [1] http://cogsci.stackexchange.com/questions/1664/what-is-the-t...
I completely agree with the general idea. Bloat is too high and has far reaching consequences. And it's actually even worse than that. 100ms is nowhere near enough to be sufficient for all applications. For audio applications you need 10ms [ http://superpowered.com/androidaudiopathlatency ] which incidentally is the reason why Android is unusable for any interactive audio applications. Same applies to Virtual Reality…
Strange. The primary use of my (Android) phone is interactive audio. I do not recognize latency as an issue.
People are OK with frequently booting their mobile devices to temporarily "fix bugs", which can take up to tens of seconds, but waiting a moment to boot a desktop device? Nuh uh. Of course there might be some market advantage to be had with faster booting and it's a plus for the whole UX. And optimisation is definitely cool, though I think many more problems would be solved if people were forced to think once in a wh…
(the steady state is that computers are running, so if it takes 30sec to cleanly shutdown then your cycle time is 31secs... obviously, this doesn't apply to stateless servers or that use write-through caching...)
What about shutdown time? (the steady state is that computers are running, so if it takes 30sec to cleanly shutdown then your cycle time is 31secs... obviously, this doesn't apply to stateless servers or that use write-through caching...)
Earlier quoted context omitted.
I would love to have a phone with a hell of a lot of stuff stripped out. I guess manufacturers don't.
Sure they do, they're called "feature phones". Wiko sells some decent dual-sim models for $20.
Earlier quoted context omitted.
Sure they do, they're called "feature phones". Wiko sells some decent dual-sim models for $20.
I have included "feature phones" in my original comment. None boot close to 1 second, and these, too, include a lot of functionality that I would like stripped out.
Earlier quoted context omitted.
> which incidentally is the reason why Android is unusable for any interactive audio applications. Everybody says this and yet programs like Caustic seem to do a fine job in my experience.
Have you tried performing using an android app? I used a drum-pad app the other week and the latency makes it unplayable. There's a great explanation here as to why it's so bad: http://superpowered.com/androidaudiopathlatency
fsk
Why isn't any phone doing it? (either smart or feature variety)
phones need to load a lot of stuff a boot time - this fast boot times are achieved by stripping a hell of a lot of stuff out
KDE used to load a session in the background when the login screen showed so that you didn't then have to wait after logging in.
On Android without root the system seems to use a ton of resources on background jobs that aren't needed; I imagine that slows boot too.