Not using C/C++ is a huge win.
-
-
We don't actually have many language options for the set of performance constraints GUI foundations require. They're all mostly C, C++, or ASM w/ scripting glue on top. Most memory safety is won via GC, which keeps busting latency budgets.
2 replies 1 retweet 4 likes -
Rust is exciting because it's memory safety without depending on GC. It's also somewhat disappointingly complex to code in. I'm sort of expecting another language that compiles to Rust. Interesting to see what happens with LLVM/Swift/Julia too.
2 replies 0 retweets 4 likes -
Any issues with Rust are very much not of the kind that you can solve by compiling another language to it.
1 reply 0 retweets 6 likes -
Let me clarify. I don't know that I see Rust solving certain issues on its own. I DO see people wanting reliable-time performance memory safety. And I'm seeing a lot of language siblings (Java/Coffee/Pure/Typescript, Lua/Terra).
1 reply 0 retweets 1 like -
As long as whatever compiles to Rust, doesn't lose Rust's security guarantees, what would we care? It's not like syntax makes you safe.
1 reply 0 retweets 0 likes -
99% of complaints about Rust are not purely syntax-related.
1 reply 0 retweets 2 likes -
What do you see as the language's tougher problems?
1 reply 0 retweets 0 likes -
The initial learning curve of the type/lifetime system for developers, especially those not familiar with C++, and compile times.
2 replies 0 retweets 2 likes -
Unless Rust abandons its core selling point ("safety by default") I don't see how you can avoid the learning curve.
1 reply 0 retweets 2 likes
Exactly. That’s why compiling to Rust doesn’t solve anything. In fact, I think the only alternatives are “be memory-unsafe” or “use GC”.
-
-
Oh come on. There's a universe of intermediate options.
2 replies 0 retweets 0 likes -
There are choices in Rust (ie making refcounting incr and allocation "explicit") that could be made differently, but there is no "intermediate" on lifetimes.
1 reply 0 retweets 1 like - 9 more replies
New conversation -
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.