Luke Hutteman's public virtual MemoryStream - Washington Post on RSS. Weblog: Luke Hutteman's public virtual MemoryStream
Source: Washington Post on RSS
Link: http://www.hutteman.com/weblog/2004/03/14-169.html
Looks like RSS is getting more mainstream press lately. After the Slate article earlier this month, today the Washington Post published an article about RSS and Aggregators. The article states
(The Post's washingtonpost.com was scheduled to begin offering a set of RSS feeds this weekend.) "was" scheduled? what went wrong? was it postponed? shot down? unfortunately there's no further mention of it in the article...
A quote Microsoft is probably not very happy about is the following in the post's coverage of RSS Reader:
It was easily the slowest newsreader we tried -- partially because it runs on Microsoft's .Net Framework, an inefficient bundle of code that lets developers add Web functions to their software. I've never used this aggregator, but I'm sure that if their performance is lagging, the fault lies in the design and implementation of the reader itself, and is not due to the .Net framework. Similarly, I've seen blog entries on the net before blaming SharpReader's memory requirements on .Net, which again is just not true. Blaming Microsoft may be the popular thing to do these days, but that doesn't mean it's always true.
The post has this to say about SharpReader:
SharpReader (Win 98 or newer, free at www.sharpreader.net) also relies on the .Net Framework, although it wasn't as slow as RSSReader. It feels unfinished in some ways: Instead of an installation routine, you have to unzip a downloaded file, then move that folder into your Program Files directory. On the other hand, it supports Atom as well as RSS and offers the most attractive, simplest interface of any Windows newsreader. I have to say I'm quite proud of SharpReader's interface being called "the most attractive and simplest of any Windows newsreader". This is exactly what I've been trying to create: a simple, easy to use interface that doesn't make you jump through hoops to get at the desired functionality. With any ideas I have about new features, I always try to think about how to best fit it into the current UI with a minimum of added complexity. If I cannot figure out how to do this, I typically rather leave out the feature than add it at the cost of a more complicated UI.
Regarding the post's comment about SharpReader's lack of an installer: I've been meaning to get to this and have been told it's a snap to do using VS.NET. I just haven't gotten around to it yet. After the Slate article earlier this month, I noticed from some of the emails I received that "xcopy deployment", while great in theory, is not what the average (non-techie) user wants. So as RSS ventures more into the mainstream this year, I'll definitely have to spend a bit of time to add that installer. [PubSub: RSS]
8:56:37 AM 
|
|
