3 ms·
There's stuff in TTY that does not belong in core (table rendering, logging), and there is a great lack of features that is available by default in [MooseX-App]
by bmn_ 12y ago
There's stuff in TTY that does not belong in core (table rendering, logging), and there is a great lack of features that is available by default in [MooseX-App](http://p3rl.org/MooseX::App http://p3rl.org/MooseX::App): bash completion, typo detection/suggestions, command words (à la `git foo`, `svn foo`).
TTY's choice of eliminating dependencies is short-sighted. By embracing dependencies, a library can be more powerful, have more features, solve more problems.
- pmurach 12y agoI've started TTY library as an extraction from another project. It was born out of necessity to keep things that are generic in another place. Even more so, a lot of TTY library is devoted to supporting table rendering, surprising or not it involves terminal properties detection, ansi strings handling etc... Thank you for pointing me to Perl library. The only thing I would say is that TTY gem does not have option parser and will probably not have one. Its main concern is more focused on prompting for values than actually providing a way to structure command line interface. There are already libraries that do an excellent job of that. Other features I will have to look individually into. I'd love to have more input on that from yourself. I have actually recently thought about the dependencies for this library. Originally I wanted to make it easy to vendor things but I have actually started extracting code from this lib as well. For example, the https://github.com/peter-murach/equatable https://github.com/peter-murach/equatable library. So I definitely agree with you and think this is the direction I'm gonna go!