21–30 of 72 posts
Yeah, its great that there are libraries like this that try to do better than the status quo. But, with every new library there's always the question about support. And so since there is no involvement perceptible on its Github page (no PRs, no issues and 3months without a commit), I wouldn't want to use this in production.
Earlier quoted context omitted.
In a horrendously framgented mobile internet, one of the few blessings we do have is that the vast majority of mobile web browsers are WebKit variants so this kind of makes a lot of sense if, say, you're only targeting iOS and Android default browsers. I'm curious if it will take jQuery plugins though. Will try later.
iOS and default Android. If you want to ignore Firefox and Opera then that’s your choice I guess.
Earlier quoted context omitted.
Agreed, ajax is usually the reason I just think fuck it and add jQuery
Or you could just look at, say, http://microjs.com/#ajax to find a nicer microlibrary to do exactly what you need.
This only supports IE10+. Why shouldn't I just use Javascript directly?
Not the author, but the API still sucks to write using vanilla JS. There are also still plenty of inconsistencies in modern browsers (per an article floating around here in the last day or two).
If you want syntactic sugar, a better alternative to a client-side library (which has overhead) is to use something like TypeScript (or one of the other compile-to-JavaScript options).
This only supports IE10+. Why shouldn't I just use Javascript directly?
The DOM API remains complete garbage unless you're operating readonly on a single node (then it's merely bad).
I have dropped jQuery completely except for when I need some of its plugins because I end up having to access the internal DOM objects too often and using $el.get(0) all over the place is ugly and a PITA.
The readme presents it as a production-ready jquery alternative but there isn't a single test written and it looks like there's no support at all
Earlier quoted context omitted.
In a horrendously framgented mobile internet, one of the few blessings we do have is that the vast majority of mobile web browsers are WebKit variants so this kind of makes a lot of sense if, say, you're only targeting iOS and Android default browsers. I'm curious if it will take jQuery plugins though. Will try later.
iOS and default Android. If you want to ignore Firefox and Opera then that’s your choice I guess.
If you want to devote dev time to specialize for the relative handful of folks who run Firefox on their mobile device, that's your call.
How this compares to zepto? As far as i know, this is basically the same promise zepto does "A kind-of-jquery but faster (and only modern boys)"
Earlier quoted context omitted.
In a horrendously framgented mobile internet, one of the few blessings we do have is that the vast majority of mobile web browsers are WebKit variants so this kind of makes a lot of sense if, say, you're only targeting iOS and Android default browsers. I'm curious if it will take jQuery plugins though. Will try later.
iOS and default Android. If you want to ignore Firefox and Opera then that’s your choice I guess.
(And even the different Webkit ports can't be thrown into the same bag.
Compare e.g. Safari on OSX, Safari on Windows, Midori on Windows and Midori on Linux. Two webkit browsers, crass rendering and behavioural differences between them and on each platform.)