-
-
Notifications
You must be signed in to change notification settings - Fork 131
progressbar Has Been Merged Into ruby progressbar
The TL;DR is that, as of version 1.8.2, ruby-progressbar
and progressbar
, while two different gems, will contain the exact same code and API.
I can't give enough thanks to Jose Peleteiro for giving me ownership of progressbar
on Rubygems. This goes a long way to giving Ruby users a single source for all of their progressbar needs... as well as a single place to focus effort to make it amazing.
You can view the history of progressbar
and ruby-progressbar
here
Some people have expressed some very... heated opinions regarding how ruby-progressbar
is architected compared to the pre-1.0 versions of progressbar
. And I do understand where they're coming from to a point.
Older versions of progressbar
...
- ...had all the code in one file. It was extremely easy to be able to look at it and read the source and fit every bit of it in your head.
- ...were slightly shorter to initialize.
But in my opinion, those pre-1.0 benefits pale in comparison to the post-1.0 features that have come about since. ruby-progressbar
had to have its README split into wiki pages because there's so much awesome stuff that it does now.
And that's not to say that I add anything and everything that's suggested. The issue history proves that's not the case. I think long and hard about adding or changing how ruby-progressbar
works to ensure it's going to be a good decision for the vast majority of users.
If neither this insight nor a glance at the wiki convinces you that the extra complexity is worth it, you're perfectly free to lock your progressbar
version to < 1.0
and continue to use the "better" version for as long as you'd like.