Time4J
Almanac Converter
| Time4J | Almanac Converter | |
|---|---|---|
| 1 | - | |
| 455 | 25 | |
| 2.2% | - | |
| 7.7 | 0.0 | |
| over 1 year ago | over 7 years ago | |
| Java | Java | |
| GNU Lesser General Public License v3.0 only | Apache License 2.0 |
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.
Time4J
-
ISO 8601: the better date format
ISO 8601 contains durations and time intervals which are totally undervalued! (https://en.wikipedia.org/wiki/ISO_8601#Time_intervals)
E.g.: 2021-05-01T12:00:00Z/P2H
They are so convenient. Every tried to store a tuple of datetimes to model a time interval? E.g. a meeting that takes place on 2021-05-01T12:00:00Z and takes two hours. Don't store it as two datetimes! Store it as an interval: "2021-05-01T12:00:00Z/P2H"
Or are you creating an API where a duration or a time interval is expected? E.g. "give me all sales in this time period..."
Please use time intervals for that. For JVM developers, there is a library out there that has amazing support: https://github.com/MenoData/Time4J
For python developers, there is pendulum which supports most of the functionality.
Almanac Converter
We haven't tracked posts mentioning Almanac Converter yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
Joda-Time - Joda-Time is the widely used replacement for the Java date and time classes prior to Java SE 8.
ThreeTenBP - Backport of functionality based on JSR-310 to Java SE 6 and 7. This is NOT an implementation of JSR-310.
iCal4j - A Java library for parsing and building iCalendar data models