Why dx11 and not 12? No one should care about win7 in 2025.
Readit NewsThaxll commented on Zed for Windows: What's Taking So Long? zed.dev/blog/windows-prog... · Posted by u/janjones
Thaxll commented on One person was able to claim 20M IPs lists.nanog.org/archives/... · Posted by u/speckx
Would be interesting to log the referer.
Thaxll commented on iPhone 16 cameras vs. traditional digital cameras candid9.com/phone-camera/... · Posted by u/sergiotapia
All recent smartphone camera are good.
I've been using sqlx with postgres for several months now on a production server with decent query volume all day long. It has been rock solid.
I find writing sql in rust with sqlx to be far fewer lines of code than the same in Go. This server was ported from Go and the end result was ~40% fewer lines of code, less memory usage and stable cpu/memory usage over time.
imo sqlc from Go is supperior to sqlx from Rust. The other thing is that sqlx is somehow slow, when I did some test, pgx ( Go ) was faster than sqlx.
Thaxll commented on I designed my own fast game streaming video codec – PyroWave themaister.net/blog/2025/... · Posted by u/Bogdanp
There is the creator of VLC that is working on something similar, very cutting edge.
https://streaminglearningcenter.com/codecs/an-interview-with...
Ultra low latency for streaming.
Thaxll commented on There is no memory safety without thread safety ralfj.de/blog/2025/07/24/... · Posted by u/tavianator
Every time this conversation comes up, I'm reminded of my team at Dropbox, where it was a rite of passage for new engineers to introduce a segfault in our Go server by not synchronizing writes to a data structure.
Swift has (had?) the same issue and I had to write a program to illustrate that Swift is (was?) perfectly happy to segfault under shared access to data structures.
Go has never been memory-safe (in the Rust and Java sense) and it's wild to me that it got branded as such.
I have a hard time believing that it's common to create SEGFAULT in Go, I worked with the language for a very long time and don't remember a single time where I've seen that. ( and i've seen many data race )
Not synchronizing writes on most data structure does not create a SEGFAULT, you have to be in a very specific condition to create one, those conditions are extremely rares and un-usual ( from the programmer perspective).
In OP blog to triggers one he's doing one of those condition in an infinite loop.
Thaxll commented on There is no memory safety without thread safety ralfj.de/blog/2025/07/24/... · Posted by u/tavianator
Yeah I understand that that's how you like to use the term, you've been very clear about that. What I am curious about is whether that's just you. Because the source you gave last time, https://www.memorysafety.org/docs/memory-safety/, doesn't agree with what you are saying, and neither does Wikipedia.
I am honestly curious here. I am a PLT researcher so I am in a bubble where people use the term consistently with how I use it. You are the first person I meet (for some notion of "meet" ;) that uses the term differently. But without external sources it's hard to judge how wide-spread your definition (that you still haven't spelled out...) is.
Go is memory safe, what do you think of: https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre...
U.S. and International Partners Issue Recommendations to Secure Software Products Through Memory Safety
They recommand Go among other language in their paper.
https://media.defense.gov/2023/Dec/06/2003352724/-1/-1/0/THE...
Thaxll commented on There is no memory safety without thread safety ralfj.de/blog/2025/07/24/... · Posted by u/tavianator
So NSA does not have the relevant authority to qualify a language as memory safe, is it what you're saying?
The document is backed by foreign government as well.
https://media.defense.gov/2023/Dec/06/2003352724/-1/-1/0/THE...
Because they have been consistently good citizens for more than 2 decades. They built a reputation. Something other companies are eager to piss away at the first opportunity to sell out or squeeze their customers.
It’s not surprising that Valve is successful and trusted with this approach. What is surprising is that it is apparently so incredibly hard for other companies to understand this very simple fact.
1. Build a good product.
2. Consistently act in good faith.
3. Profit.