3 ms·
That would be basically necessary for this kind of workflow, yeah. But the PinePhone isn’t quite at that level even; we’re talking hardware that’s going to feel
by ryukafalz 6y ago
That would be basically necessary for this kind of workflow, yeah. But the PinePhone isn’t quite at that level even; we’re talking hardware that’s going to feel unacceptably slow at fairly basic things like web browsing compared to even a low-spec x86 laptop.
Which is not to say it’s unusable, but keep in mind this is a $150 phone and the software is still a work in progress as well. If you’re expecting to use something like this docked as a workstation... well, it’s worth tempering your expectations.
- fsflover 6y ago> unacceptably slow at fairly basic things like web browsing Are you sure? https://www.youtube.com/watch?v=bH3RbrwhNd8 https://www.youtube.com/watch?v=bH3RbrwhNd8
- ryukafalz 6y ago>compared to even a low-spec x86 laptop I mean... I have a Braveheart edition PinePhone sitting right next to me, and it's usable, but I don't think I'd want to do even light development work on it. Not because an editor wouldn't run just fine on it (it probably would) but because of all the documentation I'd need to look up online during that process. It's just sluggish enough with a few webpages open to make that sound pretty unpleasant. But fair, "unacceptably slow" may have been a bit hyperbolic. (As it stands, I do have a PineTab on preorder, so... I’ll likely be giving it a try then, and that has nearly the same hardware as I understand.)
- megous 6y agoIt's not that horrible, even with large displays and a challenging dual-head output: https://www.youtube.com/watch?v=LdKNugT-mTQ https://www.youtube.com/watch?v=LdKNugT-mTQ