51–60 of 110 posts
Earlier quoted context omitted.
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
I would love to have a phone with a hell of a lot of stuff stripped out. I guess manufacturers don't.
Earlier quoted context omitted.
I used to have a Nexus 4 and had the same problem. I now have a Samsung Galaxy S3 and still have the same kinds of issues, just not as frequently. From what I've heard from other people I think it's fair to say it's a general problem with Android-based smart phones.
I have a Galaxy S3, and it was rebooting randomly more and more often. At the time, I lived in an apartment. I bought a house earlier this year, and to my knowledge (and memory) this hasn't happened again since. What you said reminded me of this, because I had forgotten this infuriating rebooting. I wonder if this was related to the building or something else? This is weird.
An OS is recomputing the same functions over and over again when booting, so why not cache all of this, and make it instant?
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 while, whether it's while waiting for the bootup sequence to complete or a train to arrive.
Earlier quoted context omitted.
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…
> 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.
There's a great explanation here as to why it's so bad: http://superpowered.com/androidaudiopathlatency
Earlier quoted context omitted.
Good point! But the hazard is that the we risk getting FOSS software that is unnecessarily complex to configure because of this.
In my experience proprietary software is often far more complex, in fact in another league than most FOSS SW for now (source: have installed and reinstalled so many Oracle databases, Enterprise Manager and APEX installations I have lost count.)
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…
Earlier quoted context omitted.
In my experience proprietary software is often far more complex, in fact in another league than most FOSS SW for now (source: have installed and reinstalled so many Oracle databases, Enterprise Manager and APEX installations I have lost count.)
Depends on the software and author. Case in point: sendmail; virtually everything ever made by RedHat (the software is free, but there's no useful documentation if you're not a paying customer… cf. NetworkManager, PulseAudio, GlusterFS … only systemd seems an exception, for now).
Earlier quoted context omitted.
I once had a brief conversation (via Reddit) with a guy using JACK for a commercial (embedded Linux) networked audio system. I wasn't aware of the exact specifics but I understand it was Sonos-style, embedded boards inside speakers. He wasn't particularly interested in talking about the work his team had done :P I think that proves your point.
This is a quite paradoxal phenomen that happens to some open source projects. The code is open and free, but some of the experts hold their knowledge very close to their chest. It's totally understandable since they of course need to make a living somehow, but it kind of defeats some of the benefits with open source.
Linux might be free and open source software, but it's not a failure of anything that it doesn't come with a free systems administrator education.
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 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.