What stuff are you missing, out of curiosity? It’s been a big goal for us lately.
-
-
Replying to @rustlang @jarrednicholls
I'm attracted to the guarantees Rust provides, but to be honest I think it's still maybe a little too low level for my use-cases. One of those "use the right tool .." scenarios, but I want to keep an eye on it!
1 reply 0 retweets 2 likes -
Last I checked cross-compiling was still difficult as well, stuff like that is pretty critical (for me)
1 reply 0 retweets 1 like -
Replying to @tjholowaychuk @jarrednicholls
Makes sense, thanks! (Cross compiling is harder than go but not super tough these days btw, working on it!)
1 reply 0 retweets 5 likes -
Replying to @rustlang @tjholowaychuk
One of the challenges with cross compiling and static builds depends on your, erm, dependencies...as some are wrappers around native libs. Pure Rust impl are very easy to cross compile, just like pure Go, whereas cgo is a pain in the butt
1 reply 0 retweets 1 like -
Replying to @jarrednicholls @rustlang
Totally, I've managed to avoid cgo entirely. Rust is super cool though I can't wait to have time to really learn it properly. I can't say I really need its power hahah.. wish I did but hey, maybe later
1 reply 0 retweets 3 likes -
Once it gets to the point where it's just as quick to develop with AND safer than the alternatives, then yeah I'm totally sold
1 reply 0 retweets 3 likes -
Fragmentation was a concern I had. I hated that in Ruby/JS, competing concurrency models for example, the fact that all Go code looks and runs in the same way is a huge productivity booster
3 replies 1 retweet 7 likes -
Replying to @tjholowaychuk @jarrednicholls
Generally async is rallying around Tokio
1 reply 0 retweets 5 likes -
And, in Node, async rallied around https://github.com/caolan/async for a while... but not anymore. Given how core async I/O is to many, would the Rust team consider standardizing Tokio in stdlib?
2 replies 0 retweets 0 likes
It would have to mature more before we’d consider it. It’s not out of the question, but there’s some rust-specific reasons why Tokio is the right choice, mostly around acceptable costs. Many options open to other ecosystems just can’t work for us.
-
-
Replying to @rustlang @tejasmanohar and
That’s not to say those options are bad for those languages! We just happen to have more significant constraints here.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.