collections

The thread is filled with people who are against recycling at collections points.

Or do you mean for Java it's better to use an imperative-style with mutating collections?

Its absolutely amazing the vast collections inside of Museum storage, most items will hardly ever see display.

Their books are out of copyright and the collections own the photographs that they took of them.

Le Guin's writing about Lord of the Rings in The Wave in the Mind, one of her nonfiction collections.

But generic code is just always going to be cray-cray (See: Haskell lenses, C++ Boost, Scala collections).

While it does avoid GC, it's mostly a faster way to share data between threads than the builtin concurrent collections.

This is a great collections of essays, I'd say bed time reading for the budding entrepreneur and/or VC.

React creates an impedance mismatch between how it is supposed to work(unidirectional data-flow + immutable collections) and how javascript actually works(everything's mutable).

The one thing I remember about Goldman Sachs is that they have their own collections library for Java.

By comparison, old-school iterating through collections is often much more difficult to refactor.

With the book collections in the original article, copyright is very clear.

Note: "library" here refers to actual libraries with books, not the programming kind, and "collections" as in "museum collection".

I doubt any legal team will just chase some random around into collections because "loser pays"

She's spot on with "don’t confuse popularity with engagement." It's not just special collections that end up as entertaining "wink wink nudge nudge nudge" content currency, but pretty much anything.