Comments on: Google Collections to the rescue http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/ Sat, 22 Nov 2008 11:42:09 +0000 http://wordpress.org/?v=2.6.3 By: Sam http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/#comment-532 Sam Thu, 24 Jul 2008 14:37:05 +0000 tag:happygiraffe.net:Article12975#comment-532 <p><span class="caps">I LOVE</span> google collections. Here is a series of blog posts by one of the guys that works on it, detailing some nice idioms:</p> <p><a href="http://publicobject.com/2007/09/series-recap-coding-in-small-with.html" rel="nofollow">http://publicobject.com/2007/09/series-recap-coding-in-small-with.html</a></p> I LOVE google collections. Here is a series of blog posts by one of the guys that works on it, detailing some nice idioms:

http://publicobject.com/2007/09/series-recap-coding-in-small-with.html

]]> By: Matt http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/#comment-531 Matt Wed, 23 Jul 2008 21:22:32 +0000 tag:happygiraffe.net:Article12975#comment-531 <p>We’ve recently incorporated Google Collections at work, and it’s chock full of useful stuff. Admittedly, much of it is the sort of thing that any decent programmer would inevitably invent for themselves at some point, but would probably not have the time or inclination to do as thorough a job as Google has. I’d like to see the best bits folded into Java 7.</p> We’ve recently incorporated Google Collections at work, and it’s chock full of useful stuff. Admittedly, much of it is the sort of thing that any decent programmer would inevitably invent for themselves at some point, but would probably not have the time or inclination to do as thorough a job as Google has. I’d like to see the best bits folded into Java 7.

]]> By: Dominic Mitchell http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/#comment-530 Dominic Mitchell Wed, 23 Jul 2008 17:51:01 +0000 tag:happygiraffe.net:Article12975#comment-530 <p>@KiLVaiDeN: I was reading from a file originally and passing on the iterator from that directly. It’s a streaming source, so it made sense to try and incorporate it into the iterator.</p> <p>As to efficiency, I very much doubt that would be an issue. The cost of IO usually dwarfs the cost of processing.</p> <p>The main point isn’t really about this particular problem. It’s more of an indication of conceptually nice the google-collections <span class="caps">API</span> is. The more I look at it, the more useful I find it.</p> @KiLVaiDeN: I was reading from a file originally and passing on the iterator from that directly. It’s a streaming source, so it made sense to try and incorporate it into the iterator.

As to efficiency, I very much doubt that would be an issue. The cost of IO usually dwarfs the cost of processing.

The main point isn’t really about this particular problem. It’s more of an indication of conceptually nice the google-collections API is. The more I look at it, the more useful I find it.

]]> By: KiLVaiDeN http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/#comment-529 KiLVaiDeN Wed, 23 Jul 2008 14:51:31 +0000 tag:happygiraffe.net:Article12975#comment-529 <p>Interesting stuff, but I think the problem is not when you need to iterate, but rather when you gather the collection at the first place.</p> <p>If your method which returns the collections doesn’t filter, order or check validity of the input data ( let it be a database filter, or something else ) you for sure need to find a way to do those steps afterwards, but usually it’s a much better design to only gather the lines you need from either a database or a file, it saves time, simplifies code, and is a much more efficient way of dealing the problems that Google Collections solve.</p> <p>My 2 cents K</p> Interesting stuff, but I think the problem is not when you need to iterate, but rather when you gather the collection at the first place.

If your method which returns the collections doesn’t filter, order or check validity of the input data ( let it be a database filter, or something else ) you for sure need to find a way to do those steps afterwards, but usually it’s a much better design to only gather the lines you need from either a database or a file, it saves time, simplifies code, and is a much more efficient way of dealing the problems that Google Collections solve.

My 2 cents
K

]]> By: Dominic Mitchell http://happygiraffe.net/blog/2008/07/22/google-collections-to-the-rescue/#comment-528 Dominic Mitchell Tue, 22 Jul 2008 14:23:57 +0000 tag:happygiraffe.net:Article12975#comment-528 <p>I missed one more that was utterly invaluable when I needed it: <a href="http://google-collections.googlecode.com/svn/trunk/javadoc/com/google/common/collect/Iterables.html#reverse(java.util.List)" rel="nofollow">Iterables.reverse()</a>.</p> I missed one more that was utterly invaluable when I needed it: Iterables.reverse().

]]>