No substance to back those points up? Ok, heres some evidence.
Lets start with WSV. With this script i am only going on what i have seen around the forum and heard from other people, oh and from Windlord himself. There are bugs in in the script so some things dont work at all or dont work right. But since windlord no longer does any scripting, these wont be fixed.
With sansan and GUS, everybody knows how bad using INIs for databases are. INI files were never meant to be used for databases, their primary purpose is for configuration data.
Once an ini file starts to get big, you will notice huge slowdowns in any script using the ini, and increased CPU/IO load.
Now we move onto psysqlite. sqlite is used nearly everywhere in the script for any sort of storage. Now, sqlite is pretty good when used for large databases and for data that changes quite a lot. but i have noticed it uses sqlite for temporary storage which gets accessed a lot. Causing high I/O and CPU load.
And onto the memory leak... Look at the following snippet:
if ($3) { return $gettok(%c,1 - $numtok(%c,44),44) | sqlite_free %result }
You will notice that it returns before freeing the result of the query, thus never removing the query from memory and creating a nice memory leak.
Heres a screenshot of a mirc running psysqlite too:
From what i remember, the server had around 14 players in game at the time.
You may have never encountered any of the issues here because most of them only really occur with a lot of players in game.
In the case of sansan/GUS, when the inis start to get large, the slowdowns will hit. That and using the old dll means mirc will spend most of its time just processing the network packets rather than producing an output for the server.
Yes, the creators were kind enough to share these scripts and nobody is saying they shouldn't have. The topic is just about which one is best, and i'm giving my opinion based on which has the least problems and uses the least resources.
All in all, best script thats not public is probably rusty/rasty (from lws). That script uses a good combination of hashes and sqlite, but uses very little ram and never uses more than 10% of a CPU core, even with a lot of players.