Earlier quoted context omitted.
I share your envy and excitement. I'm looking forward to dumping Go in favor of Rust once it's competitive in terms of libraries/stdlib. I've been building some big stuff in Go recently (mostly around financial market simulation) and the language shortcomings have hurt a lot. I've been using Go since January 2013 as my primary language, but everything I've seen of and tried with Rust is amazing.
What are the shortcomings?
Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
131–135 of 135 posts
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#132Earlier quoted context omitted.
The Rust code is both safer and faster at the cost of more keystrokes. I'm not certain the point of writing unsafe code in Haskell when there are better tools for the job. Haskell is fast enough as is and using it to hammer screws just reeks of wrong tool for the job.
As an aside, if your interested in safer and faster I'm benchmarking some of the ATS2 code examples[0] which were created for (but not yet in[1][2]) the computer language benchmarks game. It seems to beat C and C++ in some (many?) cases and create TINY binaries. I was trying to benchmark all the examples but got tired of doing it ;) Here are a couple anyway: Pidigits: $ patscc -I/home/cody/sources/ATS-Postiats-contri…
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#133Earlier quoted context omitted.
If the goal of using the less commonly used functions is performance, then it probably does. I mean: it's not like the specific problem domain needed a "less commonly used function" (e.g. you need a function to do X, where X is something that you rarely need to perform). Rather it's: "we need to code A, but we will use less commonly used functions instead of what we'd normally use for A, just to get more performance"…
>Plus, it's not like you merely exchange function f with g, while all other factors stay the same Yes, it is exactly like that. That was the point. It is literally changing out the name of a function. It has absolutely no effect on the rest of the code. Which is why the code is idiomatic by any reasonable definition.
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#134Earlier quoted context omitted.
>Plus, it's not like you merely exchange function f with g, while all other factors stay the same Yes, it is exactly like that. That was the point. It is literally changing out the name of a function. It has absolutely no effect on the rest of the code. Which is why the code is idiomatic by any reasonable definition.
If the only differences between the functions are the names and the performance characteristics, then why even bother having the slower versions? There has to be some difference somewhere, right?
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#135Earlier quoted context omitted.
Maybe "wycats" is plural and he has a team of people implementing him, like Stephen King or TJ Holowaychuk.
Note that nobody reads every post in linux-kernel. In fact, nobody who expects to have time left over to actually do any real kernel work will read even half. Except Alan Cox, but he's actually not human, but about a thousand gnomes working in under-ground caves in Swansea. None of the individual gnomes read all the postings either, they just work together really well. —Linus Torvalds (2000-05-02)