From f79ff4c81c1244380ba0ff098ba13acc66d6c00d Mon Sep 17 00:00:00 2001 From: Dion Dokter Date: Tue, 13 Aug 2024 09:40:40 +0200 Subject: [PATCH] Remove weird statistics The crates.io stats are misleading because it's a *very* incomplete list. I have no idea how crates.io defines these categories, but none of my no-std no-alloc crates are listed. I feel like listing this with such a small number of crates does a disservice to the community that has been working on making a great no-std ecosystem. Hence this PR. Let's keep it more vague while still making the point. Thanks! --- content/blog/2024-08-12-transition-announcement.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/blog/2024-08-12-transition-announcement.md b/content/blog/2024-08-12-transition-announcement.md index 746f7ee..26ce717 100644 --- a/content/blog/2024-08-12-transition-announcement.md +++ b/content/blog/2024-08-12-transition-announcement.md @@ -180,9 +180,7 @@ Our immediate focus is on the following tasks: - **Better compatibility.** - Fully switch to [quasi-pointers](https://github.com/EmbarkStudios/spirt/pull/24) to support more advanced Rust constructs. - - Add `alloc` support. This will allow us to move from supporting [at most 500 - `no_std`, no alloc crates](https://crates.io/categories/no-std::no-alloc) to [over - 6,000 `no_std` + alloc crates](https://crates.io/categories/no-std). + - Add `alloc` support. This will allow us to use even more `no_std` crates that also allocate memory. - **Better testing.** - Develop our own crater-like tool to create a burndown list of `no_std` and `alloc` crates that don't work with Rust GPU.