Google Highway
Hacker ApprovedThe most recommended of 3 SIMD libraries
Portable SIMD library that lets one binary use AVX2 or AVX-512 when available and still run on CPUs without them. Critics find its runtime dispatch and abstraction layer elaborate and bulky.
Portable SIMD library that lets one binary use AVX2 or AVX-512 when available and still run on CPUs without them. Critics find its runtime dispatch and abstraction layer elaborate and bulky.
20 people gave an opinion
- recommend it
- 15
- criticize it
- 5
- approval share
- 75%
Recommended in 8 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 15 people recommend itNeeds 10 or more, met.
- 3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 8 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
Portable SIMD across CPUs
“using Highway also means that you can detect and take advantage of e.g. AVX2 or AVX-512 in one binary that still works on CPUs without those instruction sets”
Comment from 24 Jul 2026 in “Everyone Should Know SIMD” “Highway is basically a thin wrapper over intrinsics, which you can still drop down to where it helps”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” “It's basically portable intrinsics, and a much more complete set (>300) than the ~50 in std.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” - Comment from 28 Jan 2026 in “I have written gemma3 inference in pure C”
- Comment from 25 Sep 2026 in “Fearless SIMD v1.0”
- Comment from 5 Nov 2025 on Hacker News
- Comment from 28 Sep 2026 in “The state of SIMD in Rust in 2026”
Runtime dispatch for multiple instruction sets
“using Highway also means that you can detect and take advantage of e.g. AVX2 or AVX-512 in one binary that still works on CPUs without those instruction sets”
Comment from 24 Jul 2026 in “Everyone Should Know SIMD” “Highway is my personal favourite, thanks in part for its support for runtime dispatch.”
Comment from 26 Jul 2026 in “SIMD for Collision” “portable intrinsics plus simpler runtime dispatching using our Highway library”
Comment from 25 Sep 2026 in “Fearless SIMD v1.0” - Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For”
Simpler than raw intrinsics
“Highway is basically a thin wrapper over intrinsics, which you can still drop down to where it helps”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” “Highway provides such an abstraction for arbitrary vector lengths and maps them to intrinsics.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” “It's basically portable intrinsics, and a much more complete set (>300) than the ~50 in std.”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For” - Comment from 1 Nov 2025 on Hacker News
Easy to learn and use
“Now, there is an on-ramp. A new Highway tutorial just landed in the official repo”
Comment from 18 Sep 2026 in “The Highway Tutorial” “The highway library is exactly the kind of a simpler option to use SIMD.”
Comment from 1 Nov 2025 on Hacker News “apart from that it's quite simple to use”
Comment from 17 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For”
What people warn about
Each mark is one comment
Dispatch setup is elaborate
“Highway is pretty nice but also quite elaborate when it comes to dealing with multiple vectorized versions and dispatch”
Comment from 25 Sep 2026 in “Fearless SIMD v1.0” “Runtime dispatch is still a PITA in Highway, especially compared to ISPC.”
Comment from 18 May 2026 in “C++26 Shipped a SIMD Library Nobody Asked For”
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 HighwayThis page | 15 | 5 | 75% | 8 | — | Approved |
| std::simd | 13 | 13 | 50% | 4 | — | — |
| Fearless SIMD | 8 | 0 | 100% | 3 | — | — |
What people said
31 of the 34 comments that mention it, newest first. Each links to the original comment.
“that seems to me like a bulky software abstraction layer even if it is a so-called "zero cost" abstraction”
“It’s portable SIMD done right.”
“Highway is pretty nice but also quite elaborate when it comes to dealing with multiple vectorized versions and dispatch”
“portable intrinsics plus simpler runtime dispatching using our Highway library”
“Calling it "proven" production software is a joke.”
“It is fault tolerant, distributed broker which gurantees durable queues, pub/sub and RPC all into one easy to use programming model.”
“Now, there is an on-ramp. A new Highway tutorial just landed in the official repo”
“My experience is that even two separate implementations diverge over time and I'd have low confidence in bringing the same updates and improvements to all”
“with the scope and maturity that https://github.com/google/highway brings to C++”
“Highway is my personal favourite, thanks in part for its support for runtime dispatch.”
“using Highway also means that you can detect and take advantage of e.g. AVX2 or AVX-512 in one binary that still works on CPUs without those instruction sets”
“Highway generates rather bad code as soon as you step outside a pretty narrow vertically-oriented scope”
“imo this is one of the greatest libs ever written”
“We only use Highway for our hottest hot paths that we feel benefit from that specialization.”
“I am fairly confident this is about as good as it gets in current C++.”
“Runtime dispatch is still a PITA in Highway, especially compared to ISPC.”
“It doesn’t add much value for the kind of SIMD code I write.”
“our security team has called Highway critical infrastructure and helped to harden the repo”
“it would make sense for doing my own personal programming challenges.”
“You need runtime dispatch (a la Google Highway) to solve this.”
“This is a fun way to see how well autovectorization works, with the same source code.”
“Highway is basically a thin wrapper over intrinsics, which you can still drop down to where it helps”
“Highway provides such an abstraction for arbitrary vector lengths and maps them to intrinsics.”
“It's basically portable intrinsics, and a much more complete set (>300) than the ~50 in std.”
“apart from that it's quite simple to use”
“This works quite well in practice.”
“I learned to appreciate SIMD (via highway) as one sweet spot of low-dependency portability”
“many of these benefits of ISPC can be had from explicit SIMD libraries like Google's Highway”
“but in an esotheric and not so ergonomic way.”
“In C++, this can be achieved portably using the Highway library”
“The highway library is exactly the kind of a simpler option to use SIMD.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.