/prog/ - Programming

In other words, it's just like Ruby, and to a lesser extent Python and Haskell.

If it keeps people from writing more C, then I'm all for it.

>caring about the community

Why would you do that?

Although:

https://doc.rust-lang.org/stable/book/dining-philosophers.html

fn main() {
    let p1 = Philosopher::new("Judith Butler");
    let p2 = Philosopher::new("Gilles Deleuze");
    let p3 = Philosopher::new("Karl Marx");
    let p4 = Philosopher::new("Emma Goldman");
    let p5 = Philosopher::new("Michel Foucault");
}

ayy l'Mao Zedong

>>3657

It's amazing how much code examples can say about a person.

>>3659

*cough* that fucker has been featured on https://www.reddit.com/r/socialistprogrammers …

https://www.reddit.com/r/socialistprogrammers/comments/2bxqa8/steve_klabnik_programming_for_programmers/?

>>3652

In other words, it is held hostage by Mozilla.

Servo and Rust should go to Apache, Thunderbird to LO foundation and then Mozilla could die like the cancerous "foundation" they are.

>>3676

Yeah, pretty much. More so if you consider that Mozilla is just a scheme to re-distribute "donations" among a certain SJW clique in SF.

It IS a lazy shortcut to get into systems programming without having to learn all the low level stuff.

Which is why it's so great :)

>>3767

It's not.

The learning curve is far steeper than with C and you still have to learn ALL of the low level concepts if you want to do the related low level stuff.

The thing it delivers is getting rid of a lot of unnecessary tedium like header files or retarded build systems or manually checking things the compiler can check at runtime.

Also, you don't get anything for platforms that are too small/restricted for checked things like threads/dynamic memory allocation.

>>3767

Systems guy here. Rust is currently unusable for systems work as it doesn't scale with project size and the design constraints they're working with make it unlikely they will be able to fix it. It's going to be like "merge tracking in subversion" if you remember that debacle.

>>3797

I haven't been following rust development at all, but that sounds like a fuck huge deal.

Is rust dead in the water if it is not viable as a systems language? Is there even a class of applications where rust would be an equal if not superior choice to the myriad of other options already available?

>>3797

>Rust is currently unusable for systems work as it doesn't scale with project size and the design constrai

nts they're working with make it unlikely they will be able to fix it.

More details, plox.

>>3657

>Judith Butler

yeah thanks no

>>3779

>the compiler can check at runtime

wat

>>3797

i would care to hear more about this as well

>>3893

Chances are he just lied on the internet.

>>3892

* at cumpile time

>>3659

I wonder who would be most insulted by the company?

Truthfully rust is actually much nicer than C for systems programming because of the ability to inline assembly in a way that won't make everything explode. Because you can warn the compiler what register's you're using and it then won't make any assumptions about them, which in C requires using naked functions or black magic.

>>3982

That was my impression, too.

Let's just hope, cargo doesn't turn out to be the next npm. I mean, it is technically better and more secure, but as far as I know it directly pulls from git…

>>3982

>you can warn the compiler what register's you're using

I'm pretty sure gcc's extended asm allows you to do that.

If you don't agree that rust is shit, go look up how you get input from the command line with it.

Your language isn't 'safe' if it results in your programmers attempting suicide.

>>3654

>>3652

Rust is shit because it naturally makes you do shit things.

It isn't even nice in theory. It just throws around this stupid 'safety' word as though it gives them an excuse for doing stupid shit.

>>3655

I'm a Fortran fag, so I hate C too, but Rust is far fucking worse.