Fun facts about Rust's growing popularity

Post by marcosdumay » Mon, Oct 30, 2017, 2:11 PM UTC

code_duck wrote: post #83

Someone wrote: post #35

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Rust_(fungus)

I assumed it was named after the more well-known phenomenon of iron oxidation.

Post by AlexeyBrin » Mon, Oct 30, 2017, 2:25 PM UTC

giancarlostoro wrote: post #65

terhechte wrote: post #60

Earlier quoted context omitted.

To me, Swift feels very similar to Rust only a lot simpler. Arc is also (imho) a nicer solution than a GC (though people have different opinions on that). Even better, with future versions, some of the features of Rust (i.e. lifetimes) will also come to Swift in an opt-in way. It is still a young language but fun to code in.

What's coding in Swift like outside of being on macOS? Is the tooling decent on Ubuntu / *NIX or Windows?

Post by nerpderp83 » Mon, Oct 30, 2017, 2:55 PM UTC

alkonaut wrote: post #91

randomThoughts9 wrote: post #40

Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…

I need that last drop of performance but only for a very small part of my code. For the rest, it's just painful to either have to implement iterators with tons of boilerplate ownership or declare things as sitting boxes on the heap. Both distract a lot from what I'm trying to do which is annoying. I wish there was a higher level Rust sublanguage where heap allocation and GC was default, and you would use the "bare" R…

Post by nerpderp83 » Mon, Oct 30, 2017, 3:04 PM UTC

currymj wrote: post #46

code_duck wrote: post #32

Earlier quoted context omitted.

Pythonista makes me think of a leftist guerilla in a jungle with a beret and a machine gun.

This is fairly accurate bc they have a Chairman-for-life, and a schism between two groups, one of which denounces the other as revisionist.

Post by GlitchMr » Mon, Oct 30, 2017, 4:38 PM UTC

randomThoughts9 wrote: post #80

Mouse47 wrote: post #70

Earlier quoted context omitted.

>Rusts solution is a more general solution to the "general resource problem" It's true. Ever since I got familiar with the ownership concept, I've taken to writing C# IDisposables with disposable member variables like this: public MyObject(){ this.myResource = new DisposableResource(); this.ownsMyResource = true; } public MyObject(DisposableResource resourceToUseThatIDontOwn){ this.myResource = resourceToUseThatIDont…

I agree and I appreciate what they are trying to do. But just as a counter-argument, look how a simple lock looks like in Rust [1]: fn main() { let counter = Arc::new(Mutex::new(0)); let mut handles = vec![]; for _ in 0..10 { let counter = counter.clone(); let handle = thread::spawn(move || { let mut num = counter.lock().unwrap(); *num += 1; }); handles.push(handle); } //... } [1] https://doc.rust-lang.org/book/secon…

    extern crate crossbeam;
    
    use std::sync::Mutex;
    
    fn main() {
        let counter = Mutex::new(0);
        crossbeam::scope(|scope| for _ in 0..10 {
            scope.spawn(|| *counter.lock().unwrap() += 1);
        });
        println!("{:?}", counter);
    }