The spider was very resource intensive. Let's say, it was brute-force scripting. But what was most impressive was the interface/management features, not the spidering code behind it.
I would have liked to see incremental releases of Links, with the new interfaces, bug fixes, new modules, etc. rather than one massive re-release.
The plan seems to be to make all the programs use the same engines, modules, and interfaces, and it's just the front-end .cgi scripts that will actually be different. When that happens, upgrades would really be simpler, since upgrading one program, automatically upgrades them all.
Features and changes to the programs would be done mainly in the 'scripts'not in he modules or engines.
Pretty much that is how Links SQL works now, with 90%+ of the changes made to the .cgi files, and the two interface .pm files (Links.pm and HTML_Templates.pm), with no real changes needed to the core routines in the other.pm files.
If the effort is taken further, then virtually all changes/mods/customizations would be through the interface files, not any of the core/library files.
This makes upgrades easier, since the 'functionality' is in the modules that are essentially the same from site to site, but the look/feel is in the other files which are mostly site-specific.
If the "plug-in" concept is finished, then mods/upgrades could all be plug-in, rather than code-altering changes. You add them to a plug-ins directory, and they interact with the other scripts and the databases automatically.
What's been going on, is not only a standard 'upgrade' of adding features, and fixing bugs, but a total rework of the logic to allow for future expansion, upgrade and maintennance.
http://www.postcards.com FAQ:
http://www.postcards.com/FAQ/LinkSQL/