Of course he was given a Zune. You really think he can find a copy of iTunes in order to use an iPod? I mean the odds of finding a USB interface and music in a supported encoding are already astronomically small... But at least with Zune you can just copy the files over, instead of using proprietary software.
It's been years since I've used linux, but my muscle memory for copying/pasting in the terminal is still there, to the point of it being the reason I can't use non Mac layout keyboards in OSX. I'll just keep pressing shift if I'm in the terminal.
Mobile safari was literally one of the reasons we decided to build an app instead of just having a mobile optimized website. So if that's they're strategy, it's working. Though it is a free app so it's not working _that_ well.
"Build natively" means to create it yourself in vanilla JavaScript, like this http://meandmax.github.io/lory/. What's the use of a native element that only one browser has when you need cross browser support anyway?
"Natively" as in 2 lines of CSS rather than yet another JS dependency. The cool thinks about CSS Snap Points is that they fall back rather gracefully on brothers that don't support them to just standard overflow scrolling.
Well that's not what native means. Beyond that, the issue isn't that Safari is not implementing HTML5 features fast enough, it's that they are choosing to not implement specific ones in order to protect their platform. You just don't see that from other browser vendors (today)
Isn't that the point of this article? I don't think it's fair to criticize Apple for lagging HTML5 support in iOS, then say "what's the use of this element?" when it cuts the other way.
The criticism isn't that they are lagging HTML5 support in iOS(although it would be valid- that's no reason to sue), it's that they are specifically avoiding parts of the implementation to protect their platform. Things like full screen support, notifications, etc
Are you kidding me? "Which Android" doesn't even make sense in terms of the browser, it's not tied to OS releases and is therefore the same on every phone (except freaking Samsung... Their browser is even worse than Safari). Maybe WordPress sites that need a "carousel" work better on iOS, but I can't tell you how many times I've had to go back and fix something because it won't work on iOS right. I can tell you, however, that that number is now higher than it is for ie10. So yes, it IS the new internet explorer.
