jongleberry

going to move the connect session issues here. are you going to be active maintaining this? otherwise i'm going to add people who want to help to a "session" dev...

haha okay we can figure out sessions for express 4 later then. it would probably be better just to create session middleware per store anyways. and it'll take people time...

naw. these sessions could be humongous

the problem for me is that you guys have a really complicated build system going on. i have no idea what's going on since i don't use any of these...

btw i'm working on https://github.com/detects. going to just create the detects i use as es6 modules. don't personally see a point in a giant `Modernizr` global, and how the tests...

yeah totally. my only issue with modernizr is that it uses its own complicated build system. would be nice if it used browserify or something, even if the output was...

I think this lib is pretty easy to understand. IMO they should just fork this lib if they wanna do more stuff. Most of the logic should be in separate...

You guys are just adding more responsibility to your plate hah

> Since qs will not be going this direction, we will be creating a new module and switching to that with 2.0 :+1:

the correct way imo would be to make it a constructor/prototype and expose each part as a method. then people could also do stuff like change the salt function and...