News for hackers. Stuff that matters.
Re:iOS 8 length bug breaks jQuery and Underscore object iter... by joeframbach on Tuesday March 31, 2015 @11:22PM (#9301333)
The workaround in the article was:

    var thingsGroupedById = _.groupBy(things, function(t){
      return 'seller' + t.sellerId
    });
    // { seller1: [...], seller2: [...] }
But I actually would have failed this in code review:

    _.map(thingsGroupedById, function (things) {
      // ...
    });
and replaced it with:

    _.map(_.keys(thingsGroupedById), function (thingKey) {
      var thing = thingsGroupedById[thingKey];
      // ...
    });
because although mapping over objects is "normal", it has never been 100%.
Re:iOS 8 length bug breaks jQuery and Underscore object iter... by wging on Tuesday March 31, 2015 @11:38PM (#9301381)
Why not instead do

    _.map(_.values(thingsGroupedById), function(thing) {
        // operate on thing
    }
Then there's no need to do the property access yourself.

Chaining makes this even nicer:

    _(thingsGroupedById).values().map(function(thing) {

    }
Re:iOS 8 length bug breaks jQuery and Underscore object iter... by dandelany on Wednesday April 01, 2015 @01:40AM (#9301827)
Depends on what //... is. You might need the key for something, and you can get the value from the key but not vice versa.
Re:iOS 8 length bug breaks jQuery and Underscore object iter... by gadr90 on Tuesday March 31, 2015 @11:27PM (#9301352)
This interests me very much. Are there known problems about mapping over objects? What do you mean it has never been 100%? Thanks!
Re:iOS 8 length bug breaks jQuery and Underscore object iter... by ewang1 on Tuesday March 31, 2015 @11:34PM (#9301367)
The latest version of underscore has a _.mapObject function.