3 ms·
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
by crescentfresh 15y ago
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 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.
- jbox 15y agoEspecially when parts are straight copies out of Zepto. Zepto Closest Implementation: https://github.com/madrobby/zepto/blob/master/src/zepto.js#L232 https://github.com/madrobby/zepto/blob/master/src/zepto.js#L... JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L388 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#L402 https://github.com/madrobby/zepto/blob/master/src/zepto.js#L... JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L418 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.
- rwaldron 15y agoThey didn't even bother to change the indentation whitespace...
- vjeux 15y agoI feel the same. Here's what the circles should like: http://jsfiddle.net/vjeux/DSp2m/1/ http://jsfiddle.net/vjeux/DSp2m/1/ 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...
- ehynds 15y ago"fully ready to use in production", with absolutely no unit tests, and when the question comes up it's immediately dismissed: https://github.com/appMobi/jQ.Mobi/issues/2 https://github.com/appMobi/jQ.Mobi/issues/2 Skip.
- josefrichter 15y agoFunny as hell how they closed that issue with "trying to stop flamewar" comment :D :D
- petercooper 15y agoWhy is the trashing of other developer's work necessary in promoting your own? When people like 37signals promote it as a tactic, people start to copy: http://gettingreal.37signals.com/ch02_Have_an_Enemy.php http://gettingreal.37signals.com/ch02_Have_an_Enemy.php Of relevance: One bonus you get from having an enemy is a very clear marketing message. People are stoked by conflict. And they also understand a product by comparing it to others. With a chosen enemy, you're feeding people a story they want to hear. Not only will they understand your product better and faster, they'll take sides. And that's a sure-fire way to get attention and ignite passion.