Rust 2019: Go Slow
blog.hwc.io/posts/rust-2019/Posted Dec 16, 2018, 10:01 PM UTC
Posted Dec 16, 2018, 10:01 PM UTC
Rust is running a marathon, not a sprint. Please go at a pace fit for the growing the language, its organization, its community, its people, for the long haul. I want to be programming in Rust for a long, long time.
CAN I GET A HALLELUJAH!
I am a Java programmer by trade. I have been working in Java for over twenty years now. I will be working in Java for another ten years at least, probably twenty, maybe thirty. There are mistakes made in the first few years of Java's life that still hurt us, and will still hurt us for decades to come.
If mistakes like that in Rust can be avoided by postponing a feature for six months, a year, two years, then that is very, very clearly the right thing to do if the language is going to stand the test of time. I'd rather be able to use a solid language in ten years than to boast about having the dankest async web framework next summer.
Inspired by https://boats.gitlab.io/blog/post/rust-2019/, not really polished and perhaps not fully formed, but wanted to get the gist of my ideas out there.
I was the director of the 2016 US Go Congress
lol no gener...
it was a solid half-year before I had any desire to play Go again
Oh, the game, cool.
I'm glad it's not just Rust that has this problem!
Please for love of God make RLS stable and bulletproof. I keep taking month long breaks because of how the editor integration or rls seems to break all the damn time.
It's what, two years soon since 'year of the developer'.
Completely agree, though I don't have much to add.
totally agree with you, same here
Completely agree as well! I really hope that they will not outrun themselves and make choices that they did not think carefully enough about.