Reflections on Rust, and the Sand Castle Metaphor

Post by IshKebab » Fri, Apr 27, 2018, 9:09 PM UTC

v_lisivka wrote: post #63

IshKebab wrote: post #5

I do think the difficulty of Rust is brushed aside by its proponents. This week I wrote a little script to read an XML file, get a path from it, read a file at that location, do some regexes on it, and then update the XML and write it back to disk. I'd estimate it took me about 10 times longer to implement in Rust than Python. And I don't exactly know Python well - it wasn't just extra time Googling how to do things.…

You need to type your Python code extremely fast to finish it 10 times faster than this Rust program: extern crate xpath_reader; extern crate regex; use std::io::prelude::*; use std::fs::File; use xpath_reader::Reader; use regex::Regex; fn main() { let mut contents = String::new(); File::open("test.xml").expect("Unable to open the file").read_to_string(&mut contents).expect("Unable to read the file"); //println!("Fil…

Post by cortesoft » Sat, Apr 28, 2018, 3:02 AM UTC

v_lisivka wrote: post #63

IshKebab wrote: post #5

I do think the difficulty of Rust is brushed aside by its proponents. This week I wrote a little script to read an XML file, get a path from it, read a file at that location, do some regexes on it, and then update the XML and write it back to disk. I'd estimate it took me about 10 times longer to implement in Rust than Python. And I don't exactly know Python well - it wasn't just extra time Googling how to do things.…

You need to type your Python code extremely fast to finish it 10 times faster than this Rust program: extern crate xpath_reader; extern crate regex; use std::io::prelude::*; use std::fs::File; use xpath_reader::Reader; use regex::Regex; fn main() { let mut contents = String::new(); File::open("test.xml").expect("Unable to open the file").read_to_string(&mut contents).expect("Unable to read the file"); //println!("Fil…

Post by pjmlp » Sat, Apr 28, 2018, 9:57 AM UTC

stirner wrote: post #35

lmm wrote: post #18

Earlier quoted context omitted.

Why is that the comparison point though? How long would it have taken in, say, OCaml or Haskell, which would have given similar correctness guarantees to Rust?

Neither OCaml[1] nor Haskell[2] has performance competitive with Rust. It’s impressive how many high-level functional features Rust was able to include, but it’s ultimately a systems language—and it’s unique precisely because it’s a fast systems language that can give the sorts of high-level guarantees usually reserved for GC languages. [1] http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan... [2] https://b…

Post by dbaupp » Sat, Apr 28, 2018, 1:07 PM UTC

Animats wrote: post #55

epage wrote: post #53

Earlier quoted context omitted.

From the article > This is especially true when it comes to the more complicated ones like moves and futures, but also true for simpler ones like borrows. What I didn’t know when I wrote about it in frustration a month ago is that it doesn’t take a little longer longer to be effective in Rust compared to other languages, it takes 10 to 20 times longer. I think futures might be exacerbating the authors problems. There…

Too many articles about Rust talk about why the current language sucks, but some feature in progress will fix it. Rust started out with roughly the complexity level of C++, and it's become more complex from there.

  #include 
  #include 
  #include 
    
  class Foo {
  public:
    Foo(int a) {
      std::cout  int_paren_0(0);
    std::vector int_brace_0{0};
    std::vector int_paren_2(2);
    std::vector int_brace_2{2};

    std::cout  string_paren_0(0);
    std::vector string_brace_0{0};
    std::vector string_paren_2(2);
    std::vector string_brace_2{2};

    std::cout 

  Foo 0
  Foo 0
  int_paren_0 0
  int_brace_0 1
  int_paren_2 2
  int_brace_2 1
  string_paren_0 0
  string_paren_2 2
  string_brace_2 2