home.social

#underscorejs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #underscorejs, aggregated by home.social.

fetched live
  1. Underscore v1.13.8 is out, with a security fix in _.isEqual and _.flatten. Please upgrade to underscore@latest or underscore@stable.

    github.com/jashkenas/underscor

    #javascript #security #UnderscoreJS

  2. Underscore v1.13.8 is out, with a security fix in _.isEqual and _.flatten. Please upgrade to underscore@latest or underscore@stable.

    github.com/jashkenas/underscor

    #javascript #security #UnderscoreJS

  3. @randomwizard Or use #UnderscoreJS, where most functions work the same regardless of whether you iterate over an array or an object.

    (Map and Set nog supported yet, but planned for version 2.)

  4. @randomwizard Or use #UnderscoreJS, where most functions work the same regardless of whether you iterate over an array or an object.

    (Map and Set nog supported yet, but planned for version 2.)

  5. @electricdragon I think it stems from 2 obsessions: wanting every library to be dependency-free (which is insane) and wanting to treeshake everything to the bone (which is defensible but requires shredding files because tools cannot reason about side effects). I confess I modularized #UnderscoreJS for the latter reason, though I took care to keep it readable.

    Another reason why business logic is obscure, is that nobody understands MVC anymore. The component frameworks are to blame for that.

  6. @electricdragon I think it stems from 2 obsessions: wanting every library to be dependency-free (which is insane) and wanting to treeshake everything to the bone (which is defensible but requires shredding files because tools cannot reason about side effects). I confess I modularized #UnderscoreJS for the latter reason, though I took care to keep it readable.

    Another reason why business logic is obscure, is that nobody understands MVC anymore. The component frameworks are to blame for that.

  7. @linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

  8. @linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).

  9. I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
    #JavaScript
    stackoverflow.com/a/76237929/1

  10. I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
    #JavaScript
    stackoverflow.com/a/76237929/1

  11. @noim @ph1 They are a bit niche.

    - Generating just one value: async/await is easier, as mentioned.
    - Generating a series: more likely to use events or streams or to just store everything in an array eagerly.

    Generators do allow lazy patterns, where e.g. you transform and filter a series partially with takeWhile. Lodash attempted to do such a thing before generators existed with "shortcut fusion", which was bloaty and nonscalable. #UnderscoreJS 2.0 will support generators as a collection type.