We upgraded all of our forums to 4.1.5. That includes VBForums. The other forums you listed are not ours, so I can't speak regarding them.
There are a number of tweaks I've pointed out to the developers that need to be fixed on this site. I've a list showing some are fixed and many are still in process today. You should feel free to point out specific items in this thread or the feedback forum.
As to the width - the forum should work at a smaller resolution than 1500. It works best at 1280 or higher for the width, but that covers nearly everyone coming the forum at this time. (( We know mobile devices aren't running at 1280 (yet), so we will be looking into that ))
again - any other issues you see, let us know. Even if I've already pointed them out to the developers, it doesn't hurt to have you guys mention them too.
The way I typically view a busy site is by looking at "recent posts"; I used to be able to do it on webdeveloper. With the new version, there are two options "What's new" and "new posts" that seem to produce identical results. What they don't do though is show the list of posts since I last looked, they seem to just sort all posts by when they were posted, leaving me to remember when I last viewed the list. And to see the time the posts were made (so I don't go thinking a post from 3 days ago is something I haven't looked at), I need my browser set to about 1500px wide, or the time gets cut off.
Also the number of views on posts is odd. Some posts seem to permanently have "0 views" even while they have replies. Other posts seem to have a non-zero view count.
I don't like the new [c0de][/c0de] display. The box is just too small, can't you make it stretch to 100% and give it more height, say 500-600 pixles?
Also, it might be a good idea to stop the text from wrapping, since scroll bars are implemented anyway. The code window appears to have white-space set to pre or pre-wrap, but horizontal srollbars are active.
We'll ask the devs to look at the code boxes. I believe that if we make them more dynamic that they end up getting skewed by long lines of code. I also know that when it comes to fixed widths, we have to consider the average browser width, which means that people using wide screens are going to see wasted space.
We'll run this by the devs and see what they say and can do.