Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/

Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support.

If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-…

The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.

Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/

Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support.

If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-…

The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.

Thanks for the review. If you'd like to suggest ideas, I can't recommend strongly enough that you make use of our UserVoice page. That's the primary way we're tracking requests and issues. see http://mahtweets.uservoice.com/

Regarding the request to halve the memory footprint: whilst reducing memory usage is something we'd like to see, our main goals to date have been ensuring we can provide a stable client that works well, has a good user interface, and providing good extensibility support.

If I can see that memory isn't leaking, and that it's actually being used appropriately, then a few hundred MB isn't of terrible concern (to me, atleast). The UI framework we're using (WPF) actually sits at around 50MB to start with. See: http://stackoverflow.com/questions/1288477/why-…

The cost of memory nowdays means that anything using less than a few hundred MB is really not a terribly big deal on a reasonably modern system.