I don't think EZBoard has ever gotten around to fixing longstanding issues: The generated HTML is no where near compliance - causing odd behavior even when the littlest of things is changed; the archiving issues were never addressed; the search engine is subpar; the order of the posts is time based instead of thread based; nntp will never happen; speed tends to come and go; annoying popups seem to be their business model; really long threads tend to abort in the middle (see some of the Bryce stuff on the OOP board); the user control of the L&F is minimal; the html filter makes it hard to post code - especially if the code being posted is html; etc...

Personally, I don't think EZBoard has gotten any better any time recently. Yes, they do fix some bugs, but most of those bugs are the ones introduced by the new versions. What EZBoard does have is a pretty solid backend that can send and retrieve lots of pages. What I wish they would do is make the front end as solid as the back end.

From a zIWETHEY perspective, I find it to be as fast or faster than EZBoard if I only view new messages. It does get quite slow if I try to pull up all of the messages. I suppose there might be a couple of reasons for that:

- bandwidth - as Scott mentioned

- bufferring - not sure but it appears that the entire page is buffered on the server instead of being flushed as it's being generated. If you look at some of EZBoard pages, they take a long time to download the entire page, but you get to see the top of the page before the bottom is completed.

- tables - unfortunately the browsers will not start drawing a table until the entire data for the table is received.

There's also probably a lot of issues related to Zope & PostgreSQL that Scott is probably cognizant of. At any rate, I think the software is useable at this point in time - pretty good for a prototype. I also feel that things will get better and better here, whereas on EZBoard I don't see any progress (actually seems to be regress).