News for hackers. Stuff that matters.
Re:Fil-Qt: A Qt Base build with Fil-C experience by fooker on Monday January 19, 2026 @11:52AM (#46681240)
Thread safety has not usually been a concern because it’s pretty rare to use raw threads in C++.

Rust folks always seem to assume people write C++ like it is 1995.

> implied by you questioning whether it bought any meaningful performance

This is the first thing you should always ask when you do anything with parallelism! Are you familiar with Amdahl’s law?

Re:Fil-Qt: A Qt Base build with Fil-C experience by vlovich123 on Monday January 19, 2026 @04:07PM (#46684522)
Whether you use raw threads or not in no way changes the issues around thread safety. And also I’ve worked on a lot of different codebases, from iOS at Apple to Android at Meta, from machine learning to VR video streaming. Claiming that people aren’t using raw threads in C++ a) isn’t borne out by the evidence b) is ignoring the challenges of writing thread safety code. Hell, my team hit a libc++ bug around std::conditional_var.
Re:Fil-Qt: A Qt Base build with Fil-C experience by fooker on Tuesday January 20, 2026 @04:48AM (#46689968)
IOS and related codebases at Apple are not using raw threads unless unavoidable.
Re:Fil-Qt: A Qt Base build with Fil-C experience by LexiMax on Monday January 19, 2026 @06:26PM (#46685999)
> Thread safety has not usually been a concern because it’s pretty rare to use raw threads in C++. Rust folks always seem to assume people write C++ like it is 1995.

What kind of charmed life do you lead to where use of reliable abstractions over threads is common in C++ codebases you touch?

My experience has been the exact opposite.

Re:Fil-Qt: A Qt Base build with Fil-C experience by fooker on Tuesday January 20, 2026 @04:49AM (#46689978)
> My experience has been the exact opposite

Okay, can you try and find a relatively modern large open source C++ codebase that actively uses raw threads?