Do any of you have any legitimate grievances with this language?

Do any of you have any legitimate grievances with this language?

I have seen so many of you shit-talk it you'd think atleast one of you would have some kind of intelligent argument for why it's bad.

Please note the terms "legitimate grievance" and "intelligent argument"

Attached: logo.png (225x225, 4K)

Other urls found in this thread:

youtube.com/watch?v=4t1K66dMhWk
theanarchistlibrary.org/category/author/steve-klabnik
github.com/rust-lang-deprecated/rust-buildbot/issues/2
twitter.com/AnonBabble

Everyday a new Rust thread comes up, with the OP asking us all over again why we won't chop it off and use his SJW language.
No means no, OP. We're not going to repeat all the reasons we state every single fucking thread, for you to tell us "no that's not a reason give me another". We're not going to play your game.

>SJW language.
How is this computer programming language "SJW"

>No means no, OP. We're not going to repeat all the reasons we state every single fucking thread, for you to tell us "no that's not a reason give me another". We're not going to play your game.
>I have seen so many of you shit-talk it you'd think atleast one of you would have some kind of intelligent argument for why it's bad.
I guess every time I've seen people shit-talking this language being completely vapid has just been a coincidence.

Its creators wanted to make a C replacement.
Instead they made a paperweight. Nobody can write a working program in this garbage.
Jonathan Blow absolutely destroyed it for how its main feature (the borrow checker) forces people to reinvent malloc just to make a simple program work.
Rust will never be used in production.

Its been answered a thousand million fucking times.
Its hideous.
It satisfies no niche.
It is not reliably as fast or faster than even sepples without violating its purpose and making unsafe calls.
Its developers are literal cancer and yes that is a legitimate grievance.
It barely even has concurrency and threading properly implement as a stable safe call.

Even Go is a better language because Go actually fills a niche. Rust is a solution in search of a problem and it still fails at being a solution.

Piss off.
>inb4 line by line response that refutes everything with NUHUH or HOW SO

Never gave a shit about this meme language before.
Does it use master/slave terminology?

My biggest issue with it is that there are ideas from FP languages that the rust maintainers acknowledge are good, but refuse to implement because "we want the C++ crowd"

>tail call elimination
>persistent, immutable datastructures
>higher kinded types
>dependent types

>MUH MEMORY MANAGEMENT GIMMICK
Literally C++ can do everything Rust can if you restrict yourself to the built in smart pointer types and use your brain a little bit. The only thing missing is concept support but that's coming.

>tail call elimination
Most C++ compilers already do this you know.

The Rust compiler does too.

But only with production optimizations on. Not guaranteed. They've reserved the "become" keyword for years for this purpose but it's never considered worth working on.

>How is this computer programming language "SJW"
When they go apeshit because the names in the philosophers' dinner problem are all white European males so they replace them with commies.

>Its hideous.
It looks exactly like C.

>It satisfies no niche.
You're right, it satisfies the ubiquitous desire to not have memory errors which are literally never desirable, which is not a "niche" at all.

>It is not reliably as fast or faster than even sepples without violating its purpose and making unsafe calls.
There is no inherent reason for this, it's a low-level language that operates almost exactly like C.
If it's only 90% as fast as C++ it's just because there aren't an enormous amount of RND being shovelled into it for the sheer reason that a lot of people use it.

>Its developers are literal cancer and yes that is a legitimate grievance.
If I had to use the word "cancer", I'd use it to describe someone that makes other things worse.
Like the people that believe a shotgun that fires backwards if you don't use it properly being a good feature for reasons they're never able to justify.

>It barely even has concurrency and threading properly implement as a stable safe call.
How do you "barely" have threading?

I'm going to go out on a limb here and translate that inane babble into "It has less features than C++". Which is not a bad thing, you don't want or need 7 slightly different ways to accomplish something with only one desired result. Whether or not a thread is divvied is not subjective, it is or it isn't.

>inb4 line by line response that refutes everything with NUHUH or HOW SO
It's called an argument.

It's what people that are able to formulate a rebuttal beyond ambiguous neckbeardisms that evidently immediately fall apart if you know what it is you're saying.

>"we want the C++ crowd"
Well yeah, it's meant to be a replacement to C.

It's just a different kind of tool, that doesn't need to be a bad thing.

>Literally C++ can do everything Rust can if you restrict yourself to the built in smart pointer types and use your brain a little bit
Guess what? If the library I am using doesn't follow the same pattern I can still end up with memory management problems.

On rust I know the whole ecosystem is on the same boat

It's not the use case I have an issue with. It's throwing out good ideas because they are unfamiliar to the types of programmers you want to attract.

>Guess what? If the library I am using doesn't follow the same pattern I can still end up with memory management problems.
Which is bullshit because you can always wrap the constructs it produces around with something that can satisfy your brainlet mind.

>MUH MEMORY MANAGEMENT GIMMICK
This "gimmick" is not creating errors that you literally never want to exist

I don't exaggerate when I say literally. "Error" means "erroneous". Memory is just blank canvas that you can store something on, and regardless of what's on the canvas, you never want a ripped canvas.

The more I browse this board the more I get the impression that none of you have any idea about anything. You people are sitting here sarcastically shit-talking a language that has eliminated something that's only inherently bad and hasn't been acceptable since computers were made of wood.

>On rust I know the whole ecosystem is on the same boat
>unsafe block teleports behind you
>yare yare daze
>you try to block it
>OMEIWASHINDERU
>[Translator note: you are already dead]
>It looks exactly like C.
No it doesn't, "fn" "Arc" "Box". It's fucking disgusting.
>it satisfies the ubiquitous desire to not have memory errors
Gimmick no one cares about in 2018
>If I had to use the word "cancer", I'd use it to describe someone that makes other things worse.
Like he said, you just demonstrated why the Rust community is cancer. You're so obnoxious.
>you don't want or need 7 slightly different ways to accomplish something with only one desired result. Whether or not a thread is divvied is not subjective, it is or it isn't.
Yeah there's only one right way to do things in Rust, that's surely why programmers everywhere are willing to adopt your pink hair language. Surely.
>It's called an argument.
Which you can't seem to do right. See, it's like this EVERY thread and why no one is using your shit language.

>This "gimmick" is not creating errors that you literally never want to exist
It's also a way to literally never be able to code in circular dependence when you deliberately want to. It's a restricted languages for the dumb and lazy programmer.

>It's also a way to literally never be able to code in circular dependence when you deliberately want to.
Why in god's cock would you want to you want to print "Compiling header.h" infinite times to the console when you hit compile. What are you on about

>It's a restricted languages for the dumb and lazy programmer.
That's only an insult if there's literally any good reason you would want to not have it.

A shotgun that's at 90% risk for shooting yourself instead of what you're aiming at can be argued as a good thing. A memory *****error***** is inherently bad and should never exist.

>Jonathan Blow
>I'm a genius at making games and I know it.
>I think Rust slows me down and I don't like to play by its rules.
>Therefore Rust is shit for literally everybody.
>btw I'm making my own programming language that works exactly like my autistic brain expects it to.

> t. Rustfag

Come on, let's not feed this shithead troll. I'm sure he's the worlds greatest programmer and has never overflowed an array access or used a pointer after freeing it or forgotten to check an error value. Clearly the rest of us might as well quit our jobs and take up underwater basket weaving, there's no way we can compete with his vastly superior intellect and attention to detail.

>library
You're a fucking hobbyist, what do you know? In real life your employer would have style guides that all in-house code conforms to, and all outside libraries would be vetted and have defined APIs for working with them. There are rules in place and your code works with other people's code because you all follow the rules.

Am I "trolling" you or am I serious? Pick a lane.

>I'm sure he's the worlds greatest programmer and has never overflowed an array access or used a pointer after freeing it or forgotten to check an error value.
Yes, because I use Rust.

You're trolling by being serious, you're saying what you really believe, but sarcastically, sharing your sincere oponion, with the sole intent of lying to trick people, but it comes back around to trying to tell the truth, because you're lying so hard

Not everyone lives in convoluted ironyland like you. Some people just have opinions.

Like sepples being retarded monkeys.

>Gimmick no one cares about in 2018
Congradulations for making the least intelligent comment ever posted on Jow Forums

Please collect your prize: a pile of horse shit.

Users do not give a fuck if there are errors, seriously

Congratulations for making the second least intelligent comment ever posted on Jow Forums

Please collect your prize: this bucket of rotten clam shells.

You know I thought C++ users were retarded monkeys that shouldn't be allowed around computers, but you've changed my mind (this is sarcasm).

>How is this computer programming language "SJW"
Because in order to be part of the community and have any input, you need to be a SJW and subscribe to the notion of white people being evil, particularly men.

The most known developer on the Rust core team wants to create a 'tech antifa'.

Attached: Ashley Williams, Rust Community Lead.png (1169x1001, 656K)

cry harder loser

>Rust will never be used in production.
Are you retarded? Rust is used in production. It already ships in Firefox

What does "crying" mean, complaining about something? You're doing it too

If I had to use "cry more" as an insult, I'd use it to describe the people that demand that the textual representations of the word "slave" be removed from people's computers.

>"fn"
>literally crying over a language using a different keyword for defining functions than your favorite language

ok, so you're a pajeet-tier who only knows one language and thinks shit like that matters?

>this woman's political opinions hurt my feelings!
>what a SJW c-cuck language amirite guys?
>i hate it when people make fun of my fragile masculinity!

Attached: mask.jpg (601x508, 94K)

Not everyone does things because they're insecure. As hard as it may be for you to believe.

Really, my feelings are not hurt by someone going "never underestimate the wrath of a mildly inconvenienced white dude". I'll try to recover from that savage blow.

People can call things stupid without their motive being they're insecure.

The whole Rust community is brimming with these ppl, from top to bottom. If you are not a SJW you'd be insane to invest in this language, in particular if you are a white man.

Attached: Steve Klabnik, Rust Core Team.png (638x1326, 301K)

Writing the type before the variable name comes from the earliest days of computation. It's an ancient tradition that Rust randomly throw out for no logical reason, just to be different. This isn't something to cry over, it's a reason why it will never be taken seriously or used in production.

The only people in the tech industry that support this crap are:

1. People that took a "code bootcamp" online and received a 6 figure salary to type in CSS at a leisurely pace on the back of actually skilled people
2. Actually skilled people that have heard enough reddit pseudo-intellectualism on Twitter to think that supporting these things are a good idea

There's almost no one at the core of a language design team that purports this crap like this on Twitter. Probably because anyone with any kind of intelligence thinks it's retarded.

Steve Klabnik is the creator of Rust.

It's not C or C++, useless, brings nothing of value to the table, depends on a whole lot of unsafe libraries, and has a shit community behind it that shills on Jow Forums everyday non stop for the past year.

>Writing the type before the variable name comes from the earliest days of computation
Meaning what? C?

C is a legendary language, but there's still things about it that haven't aged well. It's not good just because it's old.

>Rust randomly throw out for no logical reason, just to be different.
Putting the type after the variable makes sense if you think the type is less important information.

English language reads "red ball" as if the ball being red is more important, but every non-retarded European language reads "ball red". Rust reads like the former.

Putting the type after the variable name comes from ML, a language created in the early 1970s.

> It's not good just because it's old.

That's a retarded reason to hate something.

Alright I stand correct there.

You can be smart in one capacity, but that doesn't necessarily mean you're smart politically. It's like actors that expect to be taken seriously with their opinions on politics because people like the TV show they were in.

I'd like to think that the people that have the intelligence to design a programming language have the intelligence to understand why the textual representation of the word slave being stored on someone's computer has nothing to do with actual slavery.

Rust is pretty nice, I'd like for it to have a GC'ed pointer tbqh. Not writing kernel here. Waiting for

Fields in traits

Higher Kinded Types

Procedural macros

Const generics/pi types.

>You aren't MAN enough to accept this emasculating programming language community
LOL who are you SJWs running Rust trying to fool?

youtube.com/watch?v=4t1K66dMhWk

He is wrong on a number of points though. When you use indices like that your program is still being borrow checked. It's just that your business logic is bypassing the borrow checker, but it'll still prevent actual memory corruption.
And he says himself that you would do the same (reinventing malloc as you say) in C/C++.

His whole point is the borrow checker is useless
Just write good code

That's a terrible point.
Even if you are a very good programmer who never makes mistakes, when you're working with a team or when you're making software that will be used by others you cannot rely on that idea.
And no one is a very good programmer who never makes mistakes, not even Jonathan Blow.
He also makes single-player games so he doesn't give a shit about bugs which would be critical in many other types of software like security-related libraries, stuff that touches the network... In reality, those (especially the ones using C) are plagued with bugs that Rust is made to help a lot with.

But Rust can't help with bugs, because you can turn off the borrow checker

No you can't

Yes you can, just use an unsafe block. That's why Rust is a joke. "MUH SAFETYYYYY"

Jesus Christ you can smell the onions from the Rust conference just from this screenshot.

Attached: rust-conf.png (536x468, 193K)

Unsafe blocks don't turn off the borrow checker. All rules still apply, but you are allowed to dereference raw pointers, call unsafe functions, implement unsafe Traits and mutate statics.

Oops, looks like you shut down another average Jow Forums CS socialist with facts and logic. Now expect to be called es jay double you as a self destruct mechanism.

i feel big remorse for spending 1k+ hours in a language swarmed by sjw trash and transexual freaks

language is comfy but i wish the community could keep their mental illnesses to themselves

I don't know what Rust is, but OP seems like a faggot so I already have a negative opinion of it.

>>inb4 line by line response that refutes everything with NUHUH or HOW SO

>arguing about head-directionality of programming languages

you dipshits really have nothing better to do with your lives huh?

its a fuckin programming language. I don't give a shit who the creators are

>I'd use it to describe the people that demand that the textual representations of the word "slave" be removed from people's computers.

you know the post you're referencing was satire, right?

Woah there Chad, don't you have some thots to fuck?

im shaking, im literally shaking. a FEMOID AT MY PROGRAMMING CONFERENCE?? Giving a SPEECH NO LESS??? What has this world come to??? Why can't these femoids be happy in the kitchen?

You can't use enums for array lookups, you can't even do math on them, they're useless.
Its so fucking anal it won't implicitly convert i8 to i32 so ALL your code needs to either be the same type (it can't since you can only use usize to look up arrays) or ALL your code needs to cast EVERYTHING.
Oh, and you can't take mutable pieces of a buffer. You can only pass the whole buffer to threads or you need to use "muh egosystem" extensions to do that for you. Which ALL fucking use non-safe code so what's the fucking point of having this shit in the first fucking place?

I hate SJW shit but Rust is unironically a good language.

>t. c-hacker pissed he can't write his weakly-typed, unsafe shitcode anymore

>all outside libraries would be vetted and have defined APIs for working with them.
lmao

The BC is so trash that it unfortunately outweighs every good thing about the language.
Tagged enums, pattern matching, traits etc are great, and would be even better with metaprogramming thrown in. But the BC just completely blows all of them out of the water with it's terribleness.

borrow checker is basically a suite of unit tests pre-written for you to ensure the RAII code you're writing for lack of a garbage collector actually works

i mean, sure, theoretically neither RAII nor reference counting are effective answers to memory management in your particular program but that's not the common case, and where it is the case you can dip into unsafe and start using raw pointers - getting you slightly more noise than the cs but also enums, traits, and the borrow check making sure your normal programs are written sensibly

>borrow checker is basically a suite of unit tests pre-written for you to ensure the RAII code you're writing for lack of a garbage collector actually works
Except it's over restrictive and is therefore trash.
It prevents compilation of perfectly correct code.

yikes

Slow as fuck compile times
Macro syntax looks like pattern matching drunkenly fucked a regex
Package ecosystem is too npm-y for comfort, namespacing is flat so all the good names are either squatted or taken by shit that's abandoned.

that's like saying languages should have dynamic typing and goto because there are valid programs that use them, rather than admitting that denying more bad programs is a worthwhile thing for a compiler to do

theanarchistlibrary.org/category/author/steve-klabnik

MUH REVOLUTION

No. Types are good for optimization.
That's why statically typed compiled programs are fast.
The BC has zero optimization benefit.

>The BC has zero optimization benefit.
mut references can't alias, that info gets passed to the optimizer.

>t. NEET who never wrote a single line of Rust code

not a single technical argument, not even one, you low IQ retard

>not a single technical argument, not even one
>Performance, maintainability and stable implementation aren't technique arguments
The eternal rustoddler, everyone!

Attached: 1506112612488.png (601x508, 127K)

I only know C, and Javascript. ( I wrote a lot of node.js extensions, that you probably use )

Rust looks like an alien language and spits out errors as if they know better than a master programmer like me.

My body my choice. Stop harassing me with these questions OP. You should be banned from the Rust community.

I use C++ at work and for a couple of projects, C for about 80% of my work, and I have used Rust for a couple projects in the past.

>C++
C++ is extremely powerful, but extremely intricate. Manual memory management has its place in the world, but for most purposes it's more of an annoyance than anything else. Smart pointers are a kludge, but they're a reasonably effective one. C++ should be used when its absurd level of versatility and raw power can actually be used.

>C
C isn't as powerful as C++ in terms of its ability to put together complex high-level abstractions, but it still allows for highly granular control over the system's exact actions. The thing about C++ is that, when you don't need its advanced capabilities, those features can turn into headaches. In applications where C++'s advanced tools are unnecessary, but highly efficient code and granular control are still needed, C shines.

>Rust
Rust excels in some places, and falls short in others. It is almost impossible to avoid fighting with certain aspects of Rust's syntax to do what should be a fairly simple task. As a result, Rust has a very high learning curve from the outset (whereas C++ is easy to learn, though probably the hardest language in existence to master), and it isn't always clear what the benefit is from the headaches Rust can create.
However, Rust is unique from C++ and C in that you have to very explicitly tell Rust to fuck up in order for it to fuck up. Many common mistakes in C and C++ are very difficult to make in Rust, and this extends far beyond memory management. Its implementations of pattern matching, various fp idioms, type inference, and iterator semantics is significantly less crufty than that of C++. Rust is excellent for use cases where the codebase is extremely large, and a high degree of in-the-field stability is essential.

At least we can all agree that Go is a steaming pile of shit.

Attached: 1529936150113.png (1587x1587, 567K)

github.com/rust-lang-deprecated/rust-buildbot/issues/2

Why are Rust people so obsessed with telling others to "rewrite all your project in Rust, stop developing in C"? You are obnoxious as fuck.

Only thing built on it Firefox engine is a memory leak disaster. At least v8 is c++

>Slow as fuck compile times
This is it, the worst problem
Compiler speed needs to be a major priority
My baseline expectation is 10,000 lines/second and most good compilers can do more than that

Yikes, sweaty you reek of misogyny. It's almost as if that's why nobody likes you

Yikes, Rusties really can't meme

Web renderer has no leaks.

Firefox written in Rust leaks out the ass like blood from a man with cancer

The webrenderer is written in rust. Others C++.

Still memory leaks ever since they used the rust webrenderer.

Rust serves no purpose whatsoever.
If you want to use C++, use C++. If you want to use something higher-level, use Java or C# or Go, not something even more retarded than C++.

C++ is complex and weird but we have:

* An international (ISO) standard
* Multiple independent, conforming implementations (including 2 free ones, GCC and clang, as well as optimized vendor compilers)
* Excellent libraries to do pretty much anything (including the best GUI library, Qt, although it looks more like Java than canonical C++)
* Straight forward interfacing with C code; which gives you access to basically 99% of the most useful libraries (SQLite, Qt, SDL, you name it)
* Decades worth of articles, books, etc. (arguably, some of those are now outdated)
* A community-wide expertise amounting to billions of lines of code and decades of experience
* The programming language that basically wins all programming competitions (including the functional programming competitions...)
* C++ runs on a fucking MSP430 or an IBM mainframe

Rust fixes one issue with C++: memory safety. But it doesn't do it fully (you can still write unsafe code). So, basically, Rust brings _optional_ unsafety as opposed to C++ optional safety, and breaks many other things. BIG MOTHER FUCKING DEAL. I'm not going to switch from C++ just for this, especially if it's shit at other things.

I didn't even mention the toxic community, but it's the shit cherry on the shit cake.

memory leaks existed since long before the new webrenderer started being used.

But they were much worse now.