Danny Ayer has an interesting post on what he wants out of blog reading software.

Jäger gets tapped out at about 500 subscriptions. There are two problems in the design of Jäger that cause this. First, Jäger wants to keep a lot of information in memory — pretty well everything except the full-text content of blog postings, which is dynamically loaded at viewing time; and secondly the fact that each weblog and all its entries are stored as an individual file on your disk and thus we are limited by the speed of your filesystem which typically isn't that great.

Both these problems can be overcome, but its not a priority issue at this point. There's so much more that needs to be done for the average user before we start worrying about the outlying cases.

Jäger does have a quite powerful set of facilities for sorting through weblog content. You can set up filters to ignore certain blog postings OR to ignore all blog postings except certain ones. You can set up watch lists to highlight blog postings you're interested in AND you can mark blogs to say only show watched entries.

One of the primary failings of Jäger is the documentation for all this is scattered throughout our blog postings. Our project for Novemeber is to collect this into a coherent set of documentation.

Danny does have the right idea though. In the next major revision of the underlying guts, we should be aiming for a two or three magnitude order of improvement in the number of blogs that can be handled, not just a single order.