3 ms·

Already submitted: https://hn.algolia.com/?query=lodash&sort=byPopularity&prefix&page=0&dateRange=last24h&type=story https://hn.algolia.com/?query=lodash&sort=b

by mackwic 12y ago

Already submitted: https://hn.algolia.com/?query=lodash&sort=byPopularity&prefix&page=0&dateRange=last24h&type=story https://hn.algolia.com/?query=lodash&sort=byPopularity&prefi... Seems like no one cares. Strange.

Turing_Machine 12y ago
It's easy to not care when there's no context or indication as to what Lodash might be. Too many links, not enough time. I did click -- but only because a previous comment made it seem like Lodash was something related to functional programming. If it hadn't been for that comment, I have ignored the post, because I wouldn't have had a clue WTH Lodash was. Now, sure, people who've already used or heard of Lodash are going to know, but they're probably already following it on Github. :-) The unwashed masses like me won't have any idea. I guess the key here is to try to make the title give some indication of what the thing is.
- weavie 12y ago
  There are two kinds of JS developers, those that use LoDash at least once per function and those that have never heard of it!
arcatek 12y ago
I use Lodash but i see not point in this announcement in its current form - what changed exactly? [edit] Changelog is there https://github.com/lodash/lodash/wiki/Changelog https://github.com/lodash/lodash/wiki/Changelog Some decisions sound really weird, such as the fact that forEach is now lazy. It is not a standard replacement anymore, and probably break the compatibility for quite a few apps (even if I'm deeply convinced that we should all use the native functions and shim them when needed).
- woah 12y ago
  Are you talking about this? // in 2.4.1 _([1, 2, 3]).forEach(function(n) { console.log(n); }); // => logs each value from left to right and returns the lodash wrapper // in 3.0.0 _([1, 2, 3]).forEach(function(n) { console.log(n); }); // => returns the lodash wrapper without logging until `value` is called _([1, 2, 3]).forEach(function(n) { console.log(n); }).value(); // => logs each value from left to right and returns the array Seems that the only apps this change will break are those who are using side effects in a chain. Which is a pretty dubious choice, IMO. Especially given that Lodash is a "functional programming library".
- jkrems 12y ago
  It's only lazy when using the chaining syntax - and that one was never a standard replacement since `_.map(arr, fn)` returns a wrapper around a value and not a value.

by mackwic 12y ago

Turing_Machine 12y ago

It's easy to not care when there's no context or indication as to what Lodash might be. Too many links, not enough time. I did click -- but only because a previous comment made it seem like Lodash was something related to functional programming. If it hadn't been for that comment, I have ignored the post, because I wouldn't have had a clue WTH Lodash was. Now, sure, people who've already used or heard of Lodash are going to know, but they're probably already following it on Github. :-) The unwashed masses like me won't have any idea. I guess the key here is to try to make the title give some indication of what the thing is.

weavie 12y ago
There are two kinds of JS developers, those that use LoDash at least once per function and those that have never heard of it!

arcatek 12y ago

I use Lodash but i see not point in this announcement in its current form - what changed exactly? [edit] Changelog is there https://github.com/lodash/lodash/wiki/Changelog https://github.com/lodash/lodash/wiki/Changelog Some decisions sound really weird, such as the fact that forEach is now lazy. It is not a standard replacement anymore, and probably break the compatibility for quite a few apps (even if I'm deeply convinced that we should all use the native functions and shim them when needed).

woah 12y ago
Are you talking about this? // in 2.4.1 _([1, 2, 3]).forEach(function(n) { console.log(n); }); // => logs each value from left to right and returns the lodash wrapper // in 3.0.0 _([1, 2, 3]).forEach(function(n) { console.log(n); }); // => returns the lodash wrapper without logging until `value` is called _([1, 2, 3]).forEach(function(n) { console.log(n); }).value(); // => logs each value from left to right and returns the array Seems that the only apps this change will break are those who are using side effects in a chain. Which is a pretty dubious choice, IMO. Especially given that Lodash is a "functional programming library".
jkrems 12y ago
It's only lazy when using the chaining syntax - and that one was never a standard replacement since `_.map(arr, fn)` returns a wrapper around a value and not a value.