101–110 of 199 posts
Earlier quoted context omitted.
Why do you assume that there won't be a 4" model going forward? Do you know how many of those devices they sold? Its dead in terms of development is unwarranted exaggeration at the least.
I assume there won't be a 4" device because they didn't announce one. I'd love to find out that I'm wrong.
Earlier quoted context omitted.
I'd never run (and I'm sure a lot of people here don't either) a desktop browser without some sort of ad blocking going on I'd actually be interested to see an HN poll on this. I do not run an ad blocker and frankly I find most complaints about ads online to be totally overblown. Years ago there was a hellish amount of pop-ups, pop-overs and pop-unders, but these days I really don't have many problems, and I'm happy…
It's also worth noting that ABP is an absolute pig, on either Firefox or Chrome. I found that memory consumption and machine churn significantly dropped when I simply removed it and lived with ads. I've done no empirical measures on this, but am convinced that the cure is worse than the disease.
Credit where credit is due, the lack of customisable keyboards was a major gripe of mine when people asked me why I'd never buy an iOS device. A Swype-like keyboard (I actually use Google Keyboard's Swype mode, even though I own Swype) is a "must have" on my phone and has been for over three and a half years (since Swype beta was available on the original Galaxy Note). While there are definitely thumb typists who can…
I also find that bugs that would have gotten Apple mocked in the press and caused a massive outrage are ignored in the Android world. Namely the year or so Google Play Services would randomly lose its mind and drain your battery and the never ending Chrome bug where clicking a link just leads to an immediate page not loading condition (blank page appears and the spinning loading icon stops immediately). Heck, even the new version of Chrome does this. Thankfully not as often.
If either of these happened in the iOS world, there would be a lot of yelling a demands for fixing, as opposed to the current state where serious bugs persist for months at a time.
I'm willing to give Android L a chance before I leave. Hoepfully, we'll be seeing a higher quality of product here.
For me, that's the feature of iOS 8 I'm most excited about.
I'm really looking forward to do some hobby graphics/game development using Go and have that run on my iOS device.
Earlier quoted context omitted.
Who cares why it happens? I've gone back and forth between iOS and Android over the years and it never happens to me on my Android devices. Both platforms have their strengths and weaknesses obviously, but this used to piss me off to no end on iOS.
iOS is a little more strict about how applications use memory. Apps need to expect to be terminated at any time and be able to suspend their state with a few seconds' notice. The reason is to give you better battery life and fewer issues caused by limited available memory.
Credit where credit is due, the lack of customisable keyboards was a major gripe of mine when people asked me why I'd never buy an iOS device. A Swype-like keyboard (I actually use Google Keyboard's Swype mode, even though I own Swype) is a "must have" on my phone and has been for over three and a half years (since Swype beta was available on the original Galaxy Note). While there are definitely thumb typists who can…
I'm a little surprised that Apple included custom keyboards. They've always been an "our way or the highway" company, and custom keyboards seem like a very geek-specific feature, even if they are better to type on. Not that I'm complaining! I can finally build a couple of new apps that I wasn't able to before. :) (If anyone is interested, I'm working on a clone of the existing Apple keyboard for use as a base for dev…
Credit where credit is due, the lack of customisable keyboards was a major gripe of mine when people asked me why I'd never buy an iOS device. A Swype-like keyboard (I actually use Google Keyboard's Swype mode, even though I own Swype) is a "must have" on my phone and has been for over three and a half years (since Swype beta was available on the original Galaxy Note). While there are definitely thumb typists who can…
I installed as many keyboards as I found and tried every single one for about a day. I hated all of them. They were all different and some added interesting features, but I found that I could type fastest on my iphone's stock keyboard.
It just worked.
On my android device, I ended up restoring the stock keyboard and never looked back until I sold it and bought another iphone.
This was about 3 years ago, so maybe things changed since then.
Earlier quoted context omitted.
Who cares why it happens? I've gone back and forth between iOS and Android over the years and it never happens to me on my Android devices. Both platforms have their strengths and weaknesses obviously, but this used to piss me off to no end on iOS.
It's kinda strange, honestly: 2011's state-of-the-art Android phones (Galaxy S2) had 1GB RAM, and yet Apple is still stuck on that maximum, while Android has long moved on to 2GB on flagships. Kind of a shame :(
The only logical explanation I can come to is... more RAM won't make a meaningful impact on the experience. More ram is the cure-all on a desktop but that's not apples-to-apples.
Earlier quoted context omitted.
Who cares why it happens? I've gone back and forth between iOS and Android over the years and it never happens to me on my Android devices. Both platforms have their strengths and weaknesses obviously, but this used to piss me off to no end on iOS.
> Who cares why it happens? People who are curious about system internals. Probably some of the people who read a site like HN. Even my dad likes to understand where these limitations originate and he's not a 'computer person' (though he is an engineer in another field).
Earlier quoted context omitted.
The point of including WKWebView in the iOS 8 SDK is to make it accessible to non-Safari apps. They must have actually tested this new component. I don't doubt that there is probably an explanation that makes sense, but based on what we know, the least malicious explanation is that they forgot to test WKWebView with local files, which doesn't make sense.
"They must have actually tested this new component." Honestly, with Apple sometimes I wonder. Safari had so, so many bugs when iOS7 launched that I no longer believe they spend a meaningful amount of time testing Safari before launch.