You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting a bit upset after using hydra for a long time. I gradually realized that it actually has more cons than its pros...
Here are the main concerns in my mind that make it hard to use for both active developers and new users:
the argument specifying style of hydra is not compatible with that of other more popular CLI tools such as argparse -- while click allows us to make things argparse-like
no built-in completion: writing things in a=b style just cannot let you do auto path completion...
extended traceback... will extend the error stack substantially... making it harder to locate the real error.
inactive -- there has been a number of valuable feature requests for hydra but it is somehow unimplemented for years...
cannot add --help information for non-hydra arguments
Of course hydra has its own edge:
Keep a record of what you typed -- however I never used that... as I am just inclined to check history
Composible(?) -- well it is actually not that composable as I only find it usable by pumping things into a single main.yaml file -- this is also main reason why I found click attractive
I am getting a bit upset after using
hydra
for a long time. I gradually realized that it actually has more cons than its pros...Here are the main concerns in my mind that make it hard to use for both active developers and new users:
argparse
-- whileclick
allows us to make thingsargparse
-likea=b
style just cannot let you do auto path completion...hydra
but it is somehow unimplemented for years...--help
information for non-hydra argumentsOf course
hydra
has its own edge:history
main.yaml
file -- this is also main reason why I foundclick
attractiveProposing
click
:.yaml
which requires lots of extra configurations in package buildingAlso cc'ing active contributors for any comments: @Co1lin @Kristoff-starling
I am planning to take this into the
v0.2.0
release when we fully merged NeuRI into our main repo.The text was updated successfully, but these errors were encountered: