Why you might want to use `tome` instead

[markstos]

The sub project is stable and effective as it is, but it also several issues that haven't been addressed over the past 10 years and there's been no activity at all for a couple of years.

tome was inspired by sub and addresses several of outstanding issues with sub including:

• Support for sub-sub-commands
• Fixed ZSH completion
• Implemented Fish completion
• Ability to take advantage of updates to the upstream project (because it doesn't use code-generation).

Tome is written in Rust, which means it starts up and runs faster as well. If the above issues are important to you, tome may be better choice. But there are also some issues with Tome. I've linked to issues discussing their possible resolution with Tome:

• tome doesn't yet set variables like _SUB_ROOT for scripts
• Tome doesn't create a new binary name, but relies on modifying the shell environment. This can make it awkward to run on servers where the shell environment is not already initialized.
• The recommend installation method for Tome is to manually install a binary. Again, this makes it less friendly to use on servers that may be managed with automation and adds a new dependency, where sub only requires bash to be installed.

Despite the lack of activity in this repo, if the current feature set works for you, sub continues to work, as it only uses rather stable bash features which will continue to work for years to come.