Earlier quoted context omitted.
Is that sarcastic? Can't tell on here ;-)
Very.
Their friends all have them after they broke their iPhones so they're happy :)
Nexus 6
691–700 of 710 posts
Re: Nexus 6
#692Earlier quoted context omitted.
I have an HTC One M8, which is really tall because of the dual speakers. I also have large hands. That said, there are a few things I don't or can't use my phone for because the screen is too small, but there is almost nothing I can't do because the phone is too big. Yes, it's more comfortable in a pocket to have a smaller device, and it's better UX to be able to reach the top corner with your thumb, but I have start…
What are the few things you can't/don't use your M8 for because of its "small" screen? I have the original One, with its 4.7" screen, and have never seen the need for more than that. I only see it as cumbersome. The One is still cumbersome at times as it is, but has its benefits. I think that around 5" is the maximum sweet spot of cost/benefit from a usability standpoint though. Then again, I have never seen the need…
Just as one example, Ankidroid is pretty unpleasant on a phone, especially searching for new decks. There are quite a few other apps, too, that are "tablet optimized" for larger screens than phones have, and use internal detection to change the UI/UX you're presented with. Web usage on sites that are menu or image heavy can be problematic, too, as is working with tabular data any time. I don't enjoy watching movies/tv on my phone, either (and the battery life is horrendous).
Re: Nexus 6
#693Earlier quoted context omitted.
http://www.motorola.com/us/Nexus-6/nexus-6-motorola-us.html very bottom: Battery 3220 mAh Mixed usage up to 24 hours* Qi Wireless charging support
Good catch. OT: I hope wireless charging is there to stay. Being in robotics this is one technology that would benefit robots tremendously when it becomes more mainstream.
Wireless charging is here to stay and its been here for at least a decade. Look at Sonicare toothbrushes, they've been charging with induction for 10+ years and no one pays any attention
Re: Nexus 6
#694Earlier quoted context omitted.
I think as more of the older crowd has gotten into smart phones the screen size has gotten larger to compensate for their poor eyesight. I think this point is backed up by the fact that the rendered text size has not changed in any appreciable way.
And you'd be wrong because resolution has gone up. I can ably read very small text on a 1080p screen which I wouldn't be able to on a lower res one. The larger form factor means I can take advantage of all that extra DPI ably.
I know resolution has gone up. I didn't say otherwise. I can also read small text.
Neither of those points is an argument against what I claimed. I was stating that resolution has gone up, along with screen sizes, but that the default text rendering size has not gotten any smaller (i.e. they're not putting more stuff on the screen).
Re: Nexus 6
#695Earlier quoted context omitted.
I considered the Nokia 630, but only having 3G is a deal breaker for me. I just got the Sony Z3 compact, which is smaller than the 630, has LTE, and a bunch of other advantages (better specs all round, front-facing camera, etc.).
They do a 635 with LTE as well. I've owned a Sony android device (Xperia SP) Never again. Total bag of crap. Sold it and got a Moto G which was crap too. Neither devices could handle more than three tabs open without losing one and refreshing. The 630 can with half the RAM. I think NT scales down better than Android on handsets. I'd have got the 830 if I wanted a camera phone but I lug a Nikon D3100 around.
> I think NT scales down better than Android on handsets.
Any idea why? My only guess is because so much of Android is built on a garbage-collected, JIT-compiled environment (Dalvik), whereas much more of the Windows Phone stack relies on manual memory management and reference counting, and even .NET apps are AOT-compiled on Windows Phone. In that case, the new Android Runtime (ART) might address half the problem.
Re: Nexus 6
#696Earlier quoted context omitted.
They do a 635 with LTE as well. I've owned a Sony android device (Xperia SP) Never again. Total bag of crap. Sold it and got a Moto G which was crap too. Neither devices could handle more than three tabs open without losing one and refreshing. The 630 can with half the RAM. I think NT scales down better than Android on handsets. I'd have got the 830 if I wanted a camera phone but I lug a Nikon D3100 around.
> I think NT scales down better than Android on handsets. Any idea why? My only guess is because so much of Android is built on a garbage-collected, JIT-compiled environment (Dalvik), whereas much more of the Windows Phone stack relies on manual memory management and reference counting, and even .NET apps are AOT-compiled on Windows Phone. In that case, the new Android Runtime (ART) might address half the problem.
These reasons stick out for me:
1. NT is very small. A 66MHz / 24Mb system can still throw up a desktop.
2. The UI is entirely hardware accelerated WPF.
3. You're right about the AOT which is done off the device. It still does GC on the device for most apps which are CLR based but core WinRT stuff is manual management. NT doesn't do overcommit or mmap stuff either. Also the CLR GC runs concurrently.
4. The ecosystem isn't fragmented making centralised compilation and optimisation a reality. There are very few hardware combinations to support.
5. Better native type support in CLR. There are better unsigned and binary types in the CLR making micro-optimizations possible.
Comparing to android, Dalvik is damn slow. It seems to defer all GC until an inconvenient time and suck up lots of RAM in the process. If they get that ART compiler in there then it might be getting somewhere but I suspect from my experiments with my Moto G that the compiler has a different set of performance penalties.
Re: Nexus 6
#697Wasn't Nexus 6 the last model of replicants in Blade Runner? Just sayin'...
Re: Nexus 6
#698Another beautiful device and it is only at the cost of your privacy.
It's true. There's no selective control of permissions per app on Android. This is a glaring omission. Eg, granting permission for the app to use the internet, while denying access to your address book. This is important for maintaining control of your private data.
Google needs to do better on this front. Apple introduced selective permissions at least, but Google is way behind.
Re: Nexus 6
#699Another beautiful device and it is only at the cost of your privacy.
It's true. There's no selective control of permissions per app on Android. This is a glaring omission. Eg, granting permission for the app to use the internet, while denying access to your address book. This is important for maintaining control of your private data. Google needs to do better on this front. Apple introduced selective permissions at least, but Google is way behind.
(off topic) hey @exodust, don't forget to codepen some examples of ur web approach! https://news.ycombinator.com/item?id=8349825
Re: Nexus 6
#700Earlier quoted context omitted.
> I think NT scales down better than Android on handsets. Any idea why? My only guess is because so much of Android is built on a garbage-collected, JIT-compiled environment (Dalvik), whereas much more of the Windows Phone stack relies on manual memory management and reference counting, and even .NET apps are AOT-compiled on Windows Phone. In that case, the new Android Runtime (ART) might address half the problem.
These reasons stick out for me: 1. NT is very small. A 66MHz / 24Mb system can still throw up a desktop. 2. The UI is entirely hardware accelerated WPF. 3. You're right about the AOT which is done off the device. It still does GC on the device for most apps which are CLR based but core WinRT stuff is manual management. NT doesn't do overcommit or mmap stuff either. Also the CLR GC runs concurrently. 4. The ecosystem…
> 1. NT is very small. A 66MHz / 24Mb system can still throw up a desktop.
On what version of Windows? NT 4?