

I support knowing SIMD, but I think it’s worth mentioning that with good design depending on language and compiler you can get SIMD for free by auto vectorization.
At least Rust does this, and let’s you get away not touching explicit SIMD at all. It’s of course more fragile since you don’t always know if it’s done or not, and they can be skipped for minor changes in code and a, but with good loop hygiene you’ll get a lot of it for free.
For truly fast implementations though, handmade SIMDis usually better and faster if done correctly. And can do much more than auto vectorization can.










I don’t have a link or full context, but it turned out that the dev of tessaract (open source program for fediverse sites, involving at least spam and blocking tools) had a functionality in the program that fetched their own block list from their site. But this blocksite was blocking a huge amount of users, fediverse domains, and anything with any keywords which would be anything political, some porn/sexual terms like Yuri, and lots more. This block was completely invisible the ones running the program and would also give fediverse instances that were blocked a generic failed to connect error instead of saying blocked, preventing the fediverse instances from talking.
Seeing the above, it seems like the dev didn’t handle this discovery in any good way either and retaliated but doing this ddos thing.