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
The issue with Rust is that it's arguably harder to learn as an experienced programmer. Like he says, I'm used to skimming the guide/examples and jumping right in to writing complex code in $newlanguage. That doesn't work with Rust.
Simple examples are easy, and my first Rust program was actually a moderately complex socket proxy/mux thing which wasn't too hard to write. But now I'm trying to design a key-value store abstraction layer for a large project in Rust and still haven't figured out the lifetimes.
Jumping in the deep end is fine with most other languages, but it hurts more with Rust. Then again, it's not like I've tried, say, Haskell.
But I *get* why Rust is like this - what it's trying to do is truly novel. And I also know I can BS my way through it by using tools other languages use instead (e.g. reference counting and GCing all the things) in Rust, but I'm trying not to.
my impression has been that the issue is that other languages (esp. C++) tend to expose that kind of complexity in obvious ways, so it's reasonably easy to understand, while in Rust it's just kinda magic
The thing is typically a language either makes behind-the-scenes compromises for accessibility (Python: single-threaded/GIL, everything reference counted) or just relies on the programmer knowing what they're doing (C++).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
