SaaSHub helps you find the best software and product alternatives Learn more →
Chrono Alternatives
Similar projects and alternatives to chrono
-
-
advisory-db
Security advisory database for Rust crates published through crates.io
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
mozsearch
Mozilla code search website. (Please file bugs in bugzilla at https://mzl.la/2YtXmoN)
-
jelly-actix-web-starter
Discontinued A starter template for actix-web projects that feels very Django-esque. Avoid the boring stuff and move faster.
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
-
feedback
Discontinued Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! [Moved to: https://github.com/github-community/community]
-
-
unzrip
Unzip implementation, support for parallel decompression, automatic detection encoding
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
-
-
actix-web
Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
chrono reviews and mentions
-
Getaddrinfo() on glibc calls getenv(), oh boy
The problem is that this effects higher languages too, because they often build on libc. And on some OSes, they don't have a choice, because the system call interface is unstable and/or undocumented).
For example in rust, multiple time libraries were found to be unsound if `std::env::set_env` was ever called from a multi-threaded program. See:
https://github.com/time-rs/time/issues/293 and https://github.com/chronotope/chrono/issues/499
- Choosing the Right Rust Web Framework: An Overview
-
ZeroVer: 0-Based Versioning
> I think library authors should be more relentless and break compatibility every few years. We just need some conventions to not do so very often.
I indeed did this years ago---I'm the original author of Chrono [1]---and it wasn't well received [2] [3] [4]. To be fair, I knew it was a clear violation of semantic versioning but I didn't see any point of obeying that until we've reached 1.0 so I went ahead. People complained a lot and I had to yank the problematic release. By then I realized many enough people religiously expect semantic versioning (for good reasons though) and it's wiser to avoid useless conflict.
[1] https://github.com/chronotope/chrono
[2] https://github.com/chronotope/chrono/issues/146#issuecomment...
[3] https://github.com/chronotope/chrono/issues/156
[4] https://github.com/chronotope/chrono/blob/main/CHANGELOG.md#...
-
Simple, fast and safety alternative for unzip
On that note, it would also be good to configure cargo-deny so that a CI pipeline and any maintainer can easily audit the current dependency versions. Sometimes CVEs require a new major semver (looking at you, time 0.1.x and thus chrono 0.4.x), so it's not enough to rely on people installing the tool with semver-compatible updates. Automatically auditing dependencies is really important, and given how easy cargo-deny makes it, I don't think many projects have any excuse not to configure it.
-
Will Rust drop dependency on libc and make direct system calls? when ? (Please don't mention no_std case)
libc isn't "just a wrapper". Is a massive legacy codebase filled with hacks, UBs and bugs: https://github.com/chronotope/chrono/issues/499
-
chrono 0.4.20-rc.1 has just been released!!
Would love to have people test this, you can leave feedback here: https://github.com/chronotope/chrono/issues/674.
-
`chrono` or `time` 0.3 ?
Is it this issue? Any idea what can be done to move this along?
-
Some Mistakes Rust Doesn't Catch
In C, I've had afternoons wasted again and again by the lack of thread-safety invariant in various libraries. I've found countless bugs in Win32 APIs related to them not being thread-safe despite the documentation making no mention of that whatsoever. Including stuff that really, really ought to be thread-safe. We had the recent debacle with localtime_r in chrono which is not thread-safe due to it calling setenv. And you'd think man setenv would tell you that it's not thread-safe? Hah! Perish the thought.
-
First Impressions of Rust
https://github.com/chronotope/chrono/issues/339 for a big breaking issue I came across when using it to process some data at work. Ended up having to use python as it behaved "properly" there.
-
A note from our sponsor - SaaSHub
www.saashub.com | 28 Mar 2024
Stats
chronotope/chrono is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of chrono is Rust.