Shoutbox

And what is considered "big"?

If the topposter replies to an issue with "fixed" or "can't do" or whatever, I don't see what confusing it might be. Of course, if there is no reply and just an update in the first post, then it might.... But then again, even in the first post you could keep a history, a faq or whatever (examples exist here).

Bottom line: if the script creator handles it correctly, there shouldn't be any confusion. If the script creator doesn't handle it properly, then a subforum or even seperate threads aren't going to help fixing that either....

Anyways, Neowin is a massive forum where threads get big in no-time. Here the script threads are relative small/short. And it's only a very small handlfull of scripts that get very big threads. And most of that is due to people not reading.

And the not-reading can't be helped by subforums or multiple threads either I think. So you will still have the same amount of posts in the end, but scattered over several threads. Which on its turn leads to (more) crossposting, missing information, etc....

How many times does it occur that you need to refer people to an existing thread, or that you link to an already existing thread/post about the very same subject or that you repeat something which has been said in a very same thread? I know I encounter it a lot...

When you're going to explicitly allow and encourage different threads I think the information-scattering (and thus needed repeating of information) is only going to get worse.



As for the comparisson with skin forums. That's not very accurate I think. Because of the nature of skins, there isn't much of a discussion when someone requests something or when someone makes a release thread. I mean, with a script, everybody can and will comment on a piece of code. For skins, this is very unlikely. And for scripts you can discuss a lot of stuff about features, report bugs, request additions, etc. For skins this is again not so much.


PS: I'm not against a "requests" subforum for scripts. But only if it is used to only request a certain script and when that script is released keep the additional feature requests and everything else in that release thread. I'm a bit against having multiple (release/bug report/whatever) threads about the same script.