Live data from Hacker News

Sprint – A high-performance, DOM library for modern browsers

github.com

31–40 of 72 posts

Re: Sprint – A high-performance, DOM library for modern browsers

#31
post #12

A tiny, lightning fast jQuery-like library for modern browsers. Respectfully, this entire description is an oxymoron. Every time someone mentions a jQuery-like microlibrary, they just mean a jQuery without wide browser(-quirk) support. Browser support is a big part of what makes jQuery jQuery, and without it, you definitely get a much smaller library, but it is also very un-jQuery-like. :) Now for some praise! It mak…

JQuery themselves have two versions, one with less browser support which is apparently smaller/faster. So it's weird to say that it's not-JQuery-like. Though JQuery still recommends the bigger library for most users (unless you're embedding in a mobile app or stuff like that).

I'd love to have a streamlined but otherwise version of JQuery which I can serve to known modern web browsers. And serve the 'full' version to non-modern browsers.

Re: Sprint – A high-performance, DOM library for modern browsers

#32

Earlier quoted context omitted.

JQuery themselves have two versions, one with less browser support which is apparently smaller/faster. So it's weird to say that it's not-JQuery-like. Though JQuery still recommends the bigger library for most users (unless you're embedding in a mobile app or stuff like that).

I'd love to have a streamlined but otherwise version of JQuery which I can serve to known modern web browsers. And serve the 'full' version to non-modern browsers.

Sounds like Zepto is pretty close to what you're looking for: http://zeptojs.com/. Otherwise, jQuery 2.x is just jQuery without support for IE 6, 7 and 8. I'm not sure what kind of performance improvements it offers, but it shaves off a few kb.

Re: Sprint – A high-performance, DOM library for modern browsers

#33

Earlier quoted context omitted.

JQuery themselves have two versions, one with less browser support which is apparently smaller/faster. So it's weird to say that it's not-JQuery-like. Though JQuery still recommends the bigger library for most users (unless you're embedding in a mobile app or stuff like that).

I'd love to have a streamlined but otherwise version of JQuery which I can serve to known modern web browsers. And serve the 'full' version to non-modern browsers.

http://blog.jquery.com/2013/04/18/jquery-2-0-released/

Re: Sprint – A high-performance, DOM library for modern browsers

#34
post #24
post #5

Earlier quoted context omitted.

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).

> the API still sucks 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).

they solve different problems though... syntactic sugar from TypeScript et al solve problems with Javascript the language

jQuery solve problems with the various builtin APIs like DOM etc that are part of either Javascript or the web browser host

Re: Sprint – A high-performance, DOM library for modern browsers

#36

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)"

If you read the actual page you will see there are comparisons between Zepto, Sprint and JQuery for a bunch of it's core functions.

Yes, performance comparisons, but those could've been measurements of no-op versions of functions by the same name.

Re: Sprint – A high-performance, DOM library for modern browsers

#37
post #30

Earlier quoted context omitted.

iOS and default Android. If you want to ignore Firefox and Opera then that’s your choice I guess.

The default Android browser is no longer supported, and the embedded Chrome is blink-based and less and less webkit-ish. (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.)

Different Android vendors have versioned Chrome too and added their own quirks: http://www.quirksmode.org/blog/archives/2015/02/chrome_conti...

Re: Sprint – A high-performance, DOM library for modern browsers

#38
post #12

A tiny, lightning fast jQuery-like library for modern browsers. Respectfully, this entire description is an oxymoron. Every time someone mentions a jQuery-like microlibrary, they just mean a jQuery without wide browser(-quirk) support. Browser support is a big part of what makes jQuery jQuery, and without it, you definitely get a much smaller library, but it is also very un-jQuery-like. :) Now for some praise! It mak…

JQuery themselves have two versions, one with less browser support which is apparently smaller/faster. So it's weird to say that it's not-JQuery-like. Though JQuery still recommends the bigger library for most users (unless you're embedding in a mobile app or stuff like that).

jQuery 1.x is recommended over 2.x due to lack of IE8 support in the latter. If you don't have IE8 traffic on your site, you can safely go with 2.x (which isn't that much smaller to begin with).

Re: Sprint – A high-performance, DOM library for modern browsers

#39

There isn't a single test for this project. How can its claims of jQuery-alike-ness be supported? Tests, or it doesn't exist.

Better yet, the author should just implement the jQuery test suite, and give a rundown of what passes and what fails.
Post reply on HN