hhsnopek/pourover

A library for simple, fast filtering and sorting of large collections in the browser.

Henry Snopek

@hhsnopek

before I start changing up the methods and functions I want to get separate everything out

Tom Neyland

@TomNeyland

yeah Im interested in benchmarks as well

Henry Snopek

@hhsnopek

I just pushed up my branch

I want to do something similar to moment.js

well exactly like moment.js, take hold of es6 modules

Tom Neyland

@TomNeyland

(yay)

i was going to suggest es6 but i know not everyone is onboard the es6 train yet

but yeah thats where the future is and es5 has no sane module management

Henry Snopek

@hhsnopek

yeah so with es6 right now, babel and tracer add a lot of weight

so I don't wanna add any es6 features besides modules yet

see: https://github.com/moment/moment/tree/feature/es6-modules

Tom Neyland

@TomNeyland

thats a valid consideration, in my expierence its tracur that adds weight, babel rarely does

Henry Snopek

@hhsnopek

I agree, but for of and others start to add small weight that accumulates to be pretty big

especially with the polyfills

Tom Neyland

@TomNeyland

yeah, generators are particularly bad too

Henry Snopek

@hhsnopek

right now I'm actually working on https://github.com/carrot/share-button

we're using all of es6

and adding the polyfill

Tom Neyland

@TomNeyland

have you checked out the es6 branch of lodash?

Henry Snopek

@hhsnopek

which I'm starting to regret

I haven't

lemme take a look

YES

Tom Neyland

@TomNeyland

they have a pretty good decomposition of functionality into individual modules

Henry Snopek

@hhsnopek

that's exactly what I want to do

Tom Neyland

@TomNeyland

awesome

yeah other than bits that are a bit weird and unnecessary because of technical debt and compatability, the es6 branch of lodash is great

Henry Snopek

@hhsnopek

I really want to keep the browser support that we currently have with pourover as well

its a huge range which I love

also we need to expand the tests

Tom Neyland

@TomNeyland

yes

whats the range currently?

cant recall

Henry Snopek

@hhsnopek

IE7+
Firefox 4+
Safari 5+
Opera 9+
Chrome 1+

tbh idgaf about any of those besides IE7+

Tom Neyland

@TomNeyland

wow IE7 is the and safari 5 are the kickers there

Henry Snopek

@hhsnopek

yeah

those have to stay, huge selling point right there

Tom Neyland

@TomNeyland

yeah

Henry Snopek

@hhsnopek

I wanna figure out a way to test all the browsers on travis-ci

Tom Neyland

@TomNeyland

are there any free services that do cross browser testing?

or are you thinking some sort of container/vm travis runs

Henry Snopek

@hhsnopek

either or

idk any free services off the top of my head

Tom Neyland

@TomNeyland

the former would be preferable the latter is probably more likely the route that you'd have to go

what are your thoughts on a tiered build? like lodash offers:

Modern build (minified) - For new environments like Chrome, Firefox, IE ≥ 9, & Safari ≥ 5.1
Compatibility build (minified) - For new & old environments like IE ≤ 8 & PhantomJS

Henry Snopek

@hhsnopek

I'm fine with that, but only if it increases performance for the modern build

we could possibly do something here: https://saucelabs.com/pricing

only problem is the pricing

Tom Neyland

@TomNeyland

the rational is that there is no need to include polyfills in the modern build

Where communities thrive

People

Repo info

Activity