uwu
chrono
Our great sponsors
uwu | chrono | |
---|---|---|
24 | 23 | |
1,295 | 3,085 | |
- | 2.3% | |
0.0 | 9.7 | |
3 months ago | 3 days ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
uwu
- Discussion Thread
-
Why are there so many furry rustaceans?
Because we have the fastest uwuify library on the planet!
-
UwU as a Sewvice: API for all your uwuifying needs
Open an issue in the uwuify repo and I'll add your web server to the list of projects using uwuify!
-
all my homies use neko instead of `/usr/bin/cat`
uwuify
- deally, the cargo publish subcommand should be extended by an --nft option, so that developers can directly publish a new version of their rust project as a memex NFT.
-
uwuify - fastest test uwuifier in the west: simd vectorized and multithreaded command-line tool for text uwu-ing at the speed of simply copying a file
Sorry about the lack of docs and everything. I've made a new release 0.2.0 with a better API and better docs. There's more details in the readme about usage as a library.
-
What’s everyone working on this week (12/2021)?
Been working hard on a fast command-line tool for uwu-ing text: https://github.com/Daniel-Liu-c0deb0t/uwu I've made extensive use of simd vectorization and multithreading to get it to run as fast as file copy. Also, const fns have proved to be very useful calculating masks and stuff for string searching at compile time.
chrono
-
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.
What are some alternatives?
time - The most used Rust library for date and time handling.
av-mp4
advisory-db - Security advisory database for Rust crates published through crates.io
jelly-actix-web-starter - A starter template for actix-web projects that feels very Django-esque. Avoid the boring stuff and move faster.
UwUaaS - API for all your uwuifying needs
aho-corasick - A fast implementation of Aho-Corasick in Rust.
git-open - A command-line tool to open git project website of the containing repository.
mozsearch - Mozilla code search website. (Please file bugs in bugzilla at https://mzl.la/2YtXmoN)
chat - A telnet chat server
reqwest - An easy and powerful Rust HTTP Client
clido - A tool for creating and maintaining a todo-list on the command line
cargo-memex - compile rust code into memes