While it does leave out server rendering time, that could not possibly account for several seconds of difference. TTFB could maybe be increased by 300-500ms… 1/10th of what gains are happening here
I used to hire in a shop that did a lot of Ruby and if we were hiring for a junior position, Python was perfectly acceptable as a language to know. Knowing a dynamic language, being the type of person who teaches themselves, and being able to have visible code was what really mattered.
We found that we could drop capable juniors in a project that has some senior leadership and they were able to pick it up quickly.
Yeah, I won't learn something because somebody might think that I'm a jerk for knowing it. This is mostly due to an uninformed, judgmental, and very specific piece of the populace who won't let something go from several years ago.
Sencha and jQuery Mobile seem to be solving two very different problems. jQM delivers something that works across a variety of browsers that Sencha is not capable of serving to. Doing this will limit some of the solutions that can be put into place, for certain.
I find that with the insane amount of meetings and interruptions I might face in any given day that don't contribute to "coding time," this works really well to ensure that I'm getting things done and to keep my mind fresh. I can then engage on the business side of things later without having that nagging feeling in the back of my head that something needs to get done.
I think that if somebody just skips over programming-related things that they don't understand, it might be indicative that they are destined to be bad at programming.
As a web developer, the Android web browser is now a constant nemesis for me. It's painfully slow and it doesn't adhere to HTML5 standards worth a damn.
iOS5's mobile safari works just like regular Safari, Android's browser, I don't know what it works like, but it certainly is the first thing I'd replace when I got an Android phone.