You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Also: a recent post from the maintainer of curl seems to contradict these numbers. Is it possible your experience is not universal here?
I am just talking about the software we ship, though I suspect that if some team's bug load is mostly memory bugs, they are doing something wrong at a basic level. I don't see how memory ownership helps with logic bugs; they are pretty much orthogonal.
First, let's stop speaking in the abstract. Here is the data on curl: https://timmmm.github.io/curl-vulnerabilities-rust/ … and here is Daniel's analysis: https://daniel.haxx.se/blog/2021/03/09/half-of-curls-vulnerabilities-are-c-mistakes/ … I'm open to the idea that the curl team is doing something fundamentally wrong, but that assertion would require some evidence.
To your other point, I think working in a language with memory ownership strongly encourages a lot of patterns - context passing instead of global mutable state, "share memory by communicating", etc - that are possible but not encouraged in other languages.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
