std::simd
Ranked 2 of 3 SIMD libraries by recommenders
A portable SIMD library that people find easy to use and far less effort than intrinsics, though it is still nightly-only in Rust and critics question its level of abstraction.
A portable SIMD library that people find easy to use and far less effort than intrinsics, though it is still nightly-only in Rust and critics question its level of abstraction.
26 people gave an opinion
- recommend it
- 13
- criticize it
- 13
- approval share
- 50%
Recommended in 4 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 13 people recommend itNeeds 10 or more, met.
- 1 recommender for every criticNeeds 2 to 1 or better, not met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Easy to use, even for newcomers
“std::simd is so nice and easy to use, even as someone who's never done SIMD before”
Comment from 6 Nov 2025 in “The state of SIMD in Rust in 2025” “std::simd was what had made that problem seem approachable for the first time”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” “starting with std::simd would be much simpler for beginner.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” Good performance with less effort
“with std::simd I can get 80% of the performance with 20% of the effort compared to intrinsics”
Comment from 6 Nov 2025 in “The state of SIMD in Rust in 2025” “it's far better than the scalar ops”
Comment from 25 Sep 2026 in “Platform-independent SIMD in Go” Good enough for portable SIMD
“std::simd works well enough and should probably be stabilized”
Comment from 6 Nov 2025 in “The state of SIMD in Rust in 2025” “high level portable SIMD is usually more than good enough”
Comment from 5 Nov 2025 in “The state of SIMD in Rust in 2025” “For these use case, std.simd does the job.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” Usable today on nightly Rust
“We were okay with nightly, so we're using `std::simd` but trying to avoid the least stable APIs.”
Comment from 5 Nov 2025 in “The state of SIMD in Rust in 2025” “std::simd is perfectly usable in the state it is in today in nightly Rust.”
Comment from 6 Nov 2025 in “The state of SIMD in Rust in 2025”
What people warn about
Each mark is one comment
Still nightly-only, never stabilized
“I've written my own core::simd mimic so I don't have to make all my libs and programs use nightly.”
Comment from 5 Nov 2025 in “The state of SIMD in Rust in 2025” “why bother with any public release if it is never stable?”
Comment from 5 Nov 2025 in “The state of SIMD in Rust in 2025” “AFAIK std::simd is still nightly only”
Comment from 10 Dec 2025 in “Rust in the kernel is no longer experimental” - Comment from 24 Sep 2026 in “Fearless SIMD v1.0”
Unclear level of abstraction
“That leaves you with a definition that is doomed to be both not low level enough and too low level.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” “std::simd inherits this problem because it’s a library on top of the language, not a fix to the language.”
Comment from 22 Mar 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” Crashes across nightly versions
“I for example met chronic ICE crashes for the same code in different nightly Rust version.”
Comment from 6 Nov 2025 in “The state of SIMD in Rust in 2025” “which are as much if not more volatile than core::simd itself (and also nightly-only)”
Comment from 5 Nov 2025 in “The state of SIMD in Rust in 2025”
Other SIMD libraries people recommend
The two most recommended other SIMD libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Google Highway | 15 | 5 | 75% | 8 | — | Approved |
| std::simdThis page | 13 | 13 | 50% | 4 | — | — |
| Fearless SIMD | 8 | 0 | 100% | 3 | — | — |
What people said
29 of the 31 comments that mention it, newest first. Each links to the original comment.
“lacks the capability to emit some intrinsics”
“it's far better than the scalar ops”
“ran into the issue of swizzle_dyn needing to re-compile std”
“which still requires nightly”
“For these use case, std.simd does the job.”
“complaining that std::simd breaks portability with pre-Haswell. This is a real issue”
“shipping boondoggles like this”
“starting with std::simd would be much simpler for beginner.”
“That leaves you with a definition that is doomed to be both not low level enough and too low level.”
“The problem is that std::simd in 2026 is the 2012 solution arriving after the world moved on.”
“This leads to a potential long-term outcome where std::simd is essentially a no-op because scalar code is automagically converted into the equivalent”
“you can see a future where std::simd is essentially vestigial”
“It's for people that don't use SIMD today.”
“std::simd was what had made that problem seem approachable for the first time”
“whose quality is variable, unreliable, and which is by design always behind”
“Thanks to std::simd, now it can!”
“it is unclear who std::simd is for”
“std::simd inherits this problem because it’s a library on top of the language, not a fix to the language.”
“AFAIK std::simd is still nightly only”
“std::simd works well enough and should probably be stabilized”
“with std::simd I can get 80% of the performance with 20% of the effort compared to intrinsics”
“std::simd is perfectly usable in the state it is in today in nightly Rust.”
“std::simd is so nice and easy to use, even as someone who's never done SIMD before”
“I for example met chronic ICE crashes for the same code in different nightly Rust version.”
“high level portable SIMD is usually more than good enough”
“why bother with any public release if it is never stable?”
“which are as much if not more volatile than core::simd itself (and also nightly-only)”
“I've written my own core::simd mimic so I don't have to make all my libs and programs use nightly.”
“We were okay with nightly, so we're using `std::simd` but trying to avoid the least stable APIs.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.