groupdate
The simplest way to group temporal data (by ankane)
Recurrence
A simple library that handles recurring events. (by fnando)
groupdate | Recurrence | |
---|---|---|
2 | 2 | |
3,769 | 565 | |
- | - | |
5.9 | 0.0 | |
about 1 month ago | 10 months ago | |
Ruby | Ruby | |
MIT License | MIT 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.
groupdate
Posts with mentions or reviews of groupdate.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-16.
-
railstart-niceadmin support more features
- [groupdate](https://github.com/ankane/groupdate)
-
railstart-niceadmin release now!Backend management system based on Bootstrap 5 and NiceAdmin and Rails 7
groupdate
Recurrence
Posts with mentions or reviews of Recurrence.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-25.
-
ice_cube VS Recurrence - a user suggested alternative
2 projects | 25 Sep 2023
After a few hours of research, my observations are: - **Recurrence** is simpler to use. - **ice_cube** is more popular and more powerful.
-
Recurring events, looking for recommendations
Hi I've got a project which requires normal one off events, as well as recurring events. Looking at the resources available it seems like there are really just three gems available(montrose, recurrence and ice_cube). Of the three I've had the best results with recurrence because it allows me to pass a hash of arguments to the schedule builder. As well as handling exceptions which montrose doesn't seem to offer.
What are some alternatives?
When comparing groupdate and Recurrence you can also consider the following projects:
Chronic - Chronic is a pure Ruby natural language date parser.
ice_cube - Ruby Date Recurrence Library - Allows easy creation of recurrence rules and fast querying
time_diff - Gem which calculates the difference between two times
yymmdd - Tiny DSL for idiomatic date parsing and formatting in Ruby
biz - Time calculations using business hours.
business_time - Support for doing time math in business hours and days
time-lord - time-lord is a ruby gem that adds extra functionality to the time class.
local_time - Rails engine for cache-friendly, client-side local time
fugit - time tools (cron, parsing, durations, ...) for Ruby, rufus-scheduler, and flor