Skip to content
This repository has been archived by the owner. It is now read-only.

Merge update. #14

Closed
jdalton opened this issue Feb 13, 2016 · 5 comments
Closed

Merge update. #14

jdalton opened this issue Feb 13, 2016 · 5 comments
Labels

Comments

@jdalton
Copy link
Contributor

@jdalton jdalton commented Feb 13, 2016

Hey Ya'll, (TL;DR is at the bottom of this comment)

I wanted to give an update on the merge discussions.

On January 12 we released lodash v4. From its release notes:

The year was also one of collaboration, as discussions began on merging Lodash & Underscore. Much of Lodash v4 is proofing out the ideas from those discussions. Lodash v4 would not be possible without the collaboration & contributions of the Underscore core team. In the spirit of merging our teams have blended with several members contributing to both libraries.

It bears repeating Lodash v4 would not be possible without the collaboration & contributions of the Underscore core team. Since the merge talks began 8 months ago, with our now blended core, and combined efforts, Lodash has continued to gain ground. The following stats were reviewed by core members of both libs and are meant to show how far we've come as a whole (blended core), where our cumulative priorities are, and where the community is. (Sorry for the stats dump)

From non-core contributions (taken 2015-Feb. 2016):

LodashUnderscore
~131 contributions ~96 contributions

to number of releases (taken 2015-Feb. 2016):

LodashUnderscore
23 releases 4 releases

to number of commits (taken 2015-Feb. 2016):

LodashUnderscore
1,977 commits 422 commits

to repo traffic (taken Feb. 2016):

LodashUnderscore
Lodash has 2.8x clones, 1.8x uniq clones, 5.6x views, & 3x the uniq visitors of Underscore

to surveys:

backbone survey
developer survey

to npm package dependents (taken Feb. 2016):

dependent growth compared to npm's registry growth (taken Jul. 2015):

and growth per month (taken Oct. 2015):

Lodash is the fastest growing npm package with ~1,000 new dependents each month

even total commits year over year (taken Feb. 2016):

Lodash (up 10%)Underscore (down 65%)

With Jeremy taking a step back, Underscore core like @braddunbar @jridgewell @megawac already contributing to Lodash, combined with the community and momentum it makes sense to continue to focus our energy on Lodash.

TL;DR

So as to the merge I think it's already happened as Lodash v4. We share core contributors, @jridgewell has npm publish rights for Backbone/Lodash/Underscore, and the community has moved along with us. Thanks everyone for your input, comments, suggestions, and support!

@timdorr

This comment has been minimized.

Copy link

@timdorr timdorr commented Feb 13, 2016

This is great. Thanks for all the detail.

Is there anywhere where help is needed? Or are there already enough cooks in the kitchen?

@jdalton

This comment has been minimized.

Copy link
Contributor Author

@jdalton jdalton commented Feb 13, 2016

There's plenty to help!
We need help fleshing out our FP guide as well site design/maintenance.
Several of our repos have help wanted issue labels to identify areas to pick up.

@jdalton jdalton closed this Feb 14, 2016
@jamesplease

This comment has been minimized.

Copy link

@jamesplease jamesplease commented Feb 17, 2016

Any planz to mark Underscore as deprecated?

@akre54

This comment has been minimized.

Copy link

@akre54 akre54 commented Feb 17, 2016

Nope, not deprecated. Still pretty much status quo ante as far as I'm concerned.

@jdalton

This comment has been minimized.

Copy link
Contributor Author

@jdalton jdalton commented Feb 17, 2016

@jmeas

Any planz to mark Underscore as deprecated?

One of the benefits of the merge discussion was that it avoided making the call of ending one or the other allowing us to focus on more constructive things.

Deprecation or migration is an Underscore core call and not something Lodash core will jump into
(even though our cores overlap).

Thank you again for your support ❤️!

@underdash underdash locked and limited conversation to collaborators Feb 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.