401–410 of 486 posts
Can someone please comment on how PDF and ebooks from Manning's programming books render on Nexus 7 vs. mini-IPAD ? That, for me, is the deciding factor.
And soon enters the paradox of choice. Do I bring my smartphone, mini-tablet, tablet and/or my laptop in my bag? Wait, why did I buy all of these again?
Smartphone everywhere, mini-tablet if you're carrying a bag, Kindle if you have time to do some reading, laptop if you need to get work done. Larger tablet always stays at home. That about covers it for me, anyway. The 10" tablet now feels like the least desirable device, unless you have a relatively rare use case like reading a lot of big PDFs.
FYI, the Nexus 4 is quad core. However, the Nexus 10 is only dual! I've tried switching to a tablet at the beginning of the year but web browsing performance wasn't good enough for me. Hope the dual core downgrade won't make that much of a difference. edit: I was under the impression they both were Samsung Exynos arm processors. Turns out the Nexus 4 is using the Snapdragon S4 Pro and the Nexus 10 is using a A15 Sams…
Earlier quoted context omitted.
And with that crazy resolution.
Why is it we have amazing 16:10 2560-by-1600 in a 10" tablet but commonplace laptops (13-15") rarely surpass 1680x1050 or even worse 1366x768? Sometimes, on high-end models, you can pay an extra $200 to "upgrade" to 1920x1080 (I'll leave my rant about 16:10 vs. 16:9 for another time). Technology is so ridiculous at times.
From the viewpoint of the customer, this feels awkward. I guess the business people and engineers see it otherwise...
Earlier quoted context omitted.
In fairness to the usual suspects, their reviews of the nexus 7 were all pretty fair (and for the most part, favourable).
It didn't stop Gruber from complaining about the lack of cell data (which, thankfully, will be fixed when the $300 Nexus 7 flavor comes out).
Earlier quoted context omitted.
LTE is not as important as you make it sound. Mobile bandwidth is still expensive, so you only get a couple of GB per month for a decent price and if you want more, you have to shell out a lot of cash. I don't know how it is in the US, but here in Europe (at least in my country, Romania), the 3G connections are pretty good and 4G is coming, but it's not there yet. And I can't picture what you'd want to do with an exp…
> LTE is not as important as you make it sound. Except you then go on to explain for a couple paragraphs that it doesn't matter BECAUSE . Here is my process for connecting with my LTE phone: I turn it on. Speed is as fast as WiFi all the time. I have a 6GB plan and have never had to worry about hitting it. That's it. I haven't used a free WiFi network outside of work in a year. LTE is way faster. Just like the touchs…
With the LTE speed of 70mbps, you could use up your 6GB in 11 minutes.
It won't be long before the usual suspects start claiming - screen resolution isn't important - multi-user accounts are overly complex - low prices mean the devices are cheap and nasty
It sure wasn't long before the Google apologists started clamoring that you don't really need LTE anyway.
Earlier quoted context omitted.
> faster than we think Surface Pro, hopefully.
Surface Pro will not compete in the same space. Pricing alone will push it out of that space.
Earlier quoted context omitted.
I think many of your points are valid. In any large SDK there will be rough edges, and you have pointed out several of them. However I would like to post a contrary opinion, just because I know that many people who have never done Android development will read this and think 'yup, android development blows'. I've been working with the Android SDK for a few years now, and I haven't found any of the things you mentione…
Typically your strings are a R.strings, colours are at R.colours, etc so it makes it pretty easy to spot if you are passing a string through where you should be passing a colour. Here's the problem. Say you need to pass around a specific resource (reusable code somewhere in your app): void doSomething(int stringResourceId) ^ THIS IS WRONG The problem is that the R bullshit essentially decontextualizes what that actua…