21–30 of 43 posts
I'm very interested in this- I'm currently building an app using jQuery+jQuery Mobile and I'm very disappointed with jQM's speed. However, I'm up against a deadline, so I don't know if I'll have time to implement it, and I can't find any documentation or examples anywhere- are there any? That'll be key to working out if I can transition my code in time.
Hey, here's the git hub account w/ API examples: https://github.com/appMobi/jQ.Mobi
The graphs that depict size are misleading. The initial release (today) is already at v0.9 and the site (opened 1 week ago?) says it's "fully ready to use in production" The video aims to enumerate and demonstrate a number of issues with jQuery UI and Sencha touch ("we can't get anything to work..."). "Zepto is slow", Zepto objects are big and have "large footprints". "We polled a large group of developers...".
This is OSS. Why is the trashing of other developer's work necessary in promoting your own?
On the other hand I do appreciate that someone has delved into mobile issues and is trying to address them. But why market it like this? Why tack on "an HTML5-ready jQuery" for no (apparent) reason. CSS3 transitions aren't html5. querySelectorAll is not html5. Those other libraries don't have their problems because they are not "HTML5".
I don't know, it doesn't sit right.
Something about the marketing of this makes me feel uneasy. The graphs that depict size are misleading. The initial release (today) is already at v0.9 and the site (opened 1 week ago?) says it's "fully ready to use in production" The video aims to enumerate and demonstrate a number of issues with jQuery UI and Sencha touch ("we can't get anything to work..."). "Zepto is slow", Zepto objects are big and have "large fo…
Zepto Closest Implementation: https://github.com/madrobby/zepto/blob/master/src/zepto.js#L...
JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L3...
Zepto End Implementation: https://github.com/madrobby/zepto/blob/master/src/zepto.js#L...
JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L4...
That said, it's all open source and there are only so many ways to write these functions succinctly.
I've never had a need for JQuery on mobile. Since all mobile browsers support document.querySelector and document.querySelectorAll, I don't feel you gain that much from JQuery. That was always its killer feature on desktop. The event stuff is just sugar.
See also: “Those who cannot remember the past are condemned to repeat it.”
Edit: to downvoters, I’m not being cranky: I specifically wouldn’t use this because of this lack of compatibility and would advise against using it for the same reason (especially seeing as the couple of people I’ve pointed this out to hadn’t realised). Can you explain why you think I’m not adding to the conversation?
The semantics of the subset vary significantly from jQuery as well. Take for example the show/hide implementation. `.show()` blindly sets the display to block. jQuery remembers the value it had when you hid it (block, inline-block, table-cell, etc.) and restores that setting.
Something about the marketing of this makes me feel uneasy. The graphs that depict size are misleading. The initial release (today) is already at v0.9 and the site (opened 1 week ago?) says it's "fully ready to use in production" The video aims to enumerate and demonstrate a number of issues with jQuery UI and Sencha touch ("we can't get anything to work..."). "Zepto is slow", Zepto objects are big and have "large fo…
Also, showing benchmark for only one test doesn't follow the scientific approach.
I left a comment on the page with these two points and it has vanished...
Something about the marketing of this makes me feel uneasy. The graphs that depict size are misleading. The initial release (today) is already at v0.9 and the site (opened 1 week ago?) says it's "fully ready to use in production" The video aims to enumerate and demonstrate a number of issues with jQuery UI and Sencha touch ("we can't get anything to work..."). "Zepto is slow", Zepto objects are big and have "large fo…
Skip.
WebKit only. That might be acceptable in certain circumstances, but only if your definition of acceptability stretches to “95% of the world is on IE6; we don’t have to support anything else for our site.” See also: “Those who cannot remember the past are condemned to repeat it.” Edit: to downvoters, I’m not being cranky: I specifically wouldn’t use this because of this lack of compatibility and would advise against u…