async-pool
By jwiegley
optparse-applicative
Applicative option parser (by pcapriotti)
| async-pool | optparse-applicative | |
|---|---|---|
| - | 2 | |
| 20 | 946 | |
| - | 0.7% | |
| 0.0 | 6.4 | |
| about 2 years ago | about 2 months ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
async-pool
Posts with mentions or reviews of async-pool.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning async-pool yet.
Tracking mentions began in Dec 2020.
optparse-applicative
Posts with mentions or reviews of optparse-applicative.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-08-26.
-
Optique: Type-Safe CLI Parser Combinators
Optique was influenced by two very different libraries. One is Haskell's optparse-applicative library, which taught me that CLI parsers can be parser combinators, and that this approach is incredibly useful. The other is Zod, which TypeScript users are already familiar with. While I got the core idea from optparse-applicative, Haskell and TypeScript are such different languages that there are significant differences in how APIs are structured. So for API design, I referenced various validation libraries including Zod.
-
Powershell tab-completion script for 'optparse-applicative'-based haskell executables
Please post comments and feedback to https://github.com/pcapriotti/optparse-applicative/pull/420
What are some alternatives?
When comparing async-pool and optparse-applicative you can also consider the following projects:
prefork
optparse-declarative - Declarative command-line option parser
turtle - Shell programming, Haskell style
lens-process - Optics for system processes
nix-deploy - Deploy software or an entire NixOS system configuration to another NixOS system
optparse-generic - Auto-generate a command-line parser for your datatype