>Stop programming in C, we need to get more Rust programm

File: 19905420.jpg (31KB, 480x426px) Image search: [Google]

31KB, 480x426px

>>61456733
>Death to C++
I'm on board

>>61456766
>pic
kekeke

>>61456733
>>61456766
Ferris is the best girl.

>>61456733
>source isn't lewd
Stop this.

Death to java

>>61457307
(male)

how employable are you if you know Rust?

>>61457383
Very

File: 1497980115368.gif (2MB, 540x540px) Image search: [Google]

2MB, 540x540px

so do we like ferris or what?
i am in love with her (male)

>>61457378
Who cares?

C and C++ will literally never die. It can't

>>61457437
Lol

>>61457396
We like her because she is a sexy and cute girl can't have kids.

>>61457437
I wouldn't say never, but they'll both outlast everyone in this thread. Not to mention rust (lol).

>>61457394

im in Seattle and i search on CL "rust" got no results for seattle area, but got some c++ results

explain yourself.

>>61456733
No one here is programming C, /g/ is just a bunch of pajeets and juniors who are writing hello-worlds in C and Haskell because it's cool.

>>61457502
I was joking

>>61457506
I regularly program in C - nothing else comes close in terms of performance when writing simulation software (t. Physicist).

Rust is a meme language which will die out within a few years. C isn't going anywhere, it will outlive everyone here and probably our grandchildren too.

>>61457307
>girl

>>61457396
>her
>>61457479
>she

>>61457578
Have you written in rust? Have you benchmarked perf difference?

>>61457616
I'm not about to convert my entire code-base from C to rust. Even if I had the time I wouldn't do it, rust syntax is horrible and the language is not as reputable (and not as reliable) as C.

>>61457331
Where is the source?

>>61457590
>>61457605
A cute(male) girl still a girl.

>>61456733
>C
>rust
Babby tier, real programmers code in Assembly. Yeah, in 1s and 0s

>The C programming language is terrible. I mean, magnificent, too.

Yeah that about sums up this meaningless shill article.

People who don't know the SystemV ABI shouldn't be allowed to blog like retards about C.

File: 1470864652383.jpg (390KB, 1920x1080px) Image search: [Google]

390KB, 1920x1080px

>>61457396

I too love Ferris.

>>61457660
Wait, so you don't really have any basis for saying C is faster in most cases, but you still feel like sharing your opinions. I bet you're into string theory :^)

Rust is already beating C and C++ in performance in pretty much everything that's been ported to it. It's the future. Only amateurs from /g/ who are too dumb to learn it will refuse to use it, everyone else can plainly see it's a superior alternative with no downsides.

>>61457760
Get out of here, C is faster than rust. I'm not going to change my code-base to a slower language which has disgusting syntax costing me valuable time and money. And, no, I'm not a particle physicist.

Did you know that felix is not gay?
He gets more pussy than you.

>>61456733
They should take their meme language and fuck off.

>>61457805
you mean dicks

Pretty much anyone who puts C and C++ on the same sentence like they're interchangeable doesn't know what they're talking about.

>>61457803
Proofs?

File: 1471440557059.png (247KB, 500x411px) Image search: [Google]

247KB, 500x411px

Never programmed C or hardly anything but now theres 20 credits mandated in curriculum

What am I in for?

>>61457847
autism

>>61457847
you'll live

>>61457834
There's plenty out there. Do you want me to hold your hand too?

>>61457803
Maybe you should stop polluting the internet with your gut feeling evidence-less posts? You'd think someone working as a physicist would be a little more into the whole proof thing, but seems not.

That said I also believe C is the correct choice for many applications, but I also think there's a huge cargo-cult mentality surrounding it and it is most definitely used a lot of places where it shouldn't, leading to avoidable bugs.

>>61457803
Rust wins in most benchmarks desu

>>61457866
Usually when you make a claim, you back it up with some evidence.

>>61457884
>Maybe you should stop polluting the internet with your gut feeling evidence-less posts?
I don't have time to compile a good, varied list of benchmarks for C compared to rust. Why are there always so many fucking rust shills whenever a C/rust thread appears? I stick to my position that rust will die out whilst C will still be going strong within a few years time.

>>61457890
In benchmarks tailored for that 'language' to win.

File: cs.png (116KB, 1515x663px) Image search: [Google]

116KB, 1515x663px

>>61457957
All I ask is that you stop spreading unfounded bullshit opinions unless you've bothered to benchmark. I would imagine this shouldn't be news to a fellow scientist, but apparently it has escaped you.

>>61457987
Alright you show me a consistent and varied set of benchmark data which implies Rust is faster than C then. Most benchmarks I've seen show the exact opposite except for a few very specific situations.

>>61457884
Nobody uses C for "efficiency" anymore kiddo. Nobody actually cares about bugs either. People use it because you can actually interoperate with C programs. C and SystemV ABI are pretty much designed around each other.

Use something as simple as function overloading in C++ and your program is no longer guaranteed to be interoperable with even C++ code. Java and C# are 100% virtualized, meaning you'll have to bring the entire xboxhueg VM into your process if you want to talk to a program. The only way out it I/O, which means system calls.

There's a reason people wrote things like libgit2 in C. They wanted everyone to be able to use it.

>>61457847
Undefined behavior.

>>61456733
The thing is as much I love Rust and dislike C, which I get paid to write, IMO you need to understand C to what makes Rust great and why C should be avoided if possible. Ifeel like if I first started learning systems programming on Rust I'd be hella confused.

>>61457959
What's your source, NSA shill?

Daily reminder that NSA regularly shills C because they want people to write vulnerable code in critical systems.

>>61457660
>(and not as reliable) as C

>C
>reliable

toppest of the keks

File: 1495730398557.jpg (75KB, 750x728px) Image search: [Google]

75KB, 750x728px

>>61457957
>is asked evidence for his claims
>"rust shills"
Speed of the program can be increased by hundreds of times when writing code that utilizes your hardware properly (multi-core CPUs and GPUs) and doing general optimization. The performance difference between Rust and C (~1.2) is meaningless, especially considering what features you gain from it.

>>61458081
W O K E
O
K
E

>>61456733
good, I like Rust better

>>61458027
Rust usually gets beaten by C, I'm not arguing that fact. It's just that I sincerely doubt you've run any real benchmarks on the difference between them, and I also believe if you used a language such as rust or nim for the less hot code it would give you more time to optimize the hot parts of your program.

Mostly I think your attitude is really childish, as if you believe C would fall out of prominence if not for people like you defending it whenever someone dares to suggest it's not the perfect language.

>>61457693
ferris is a qt trap not a girl (male)

>>61456733
Has the purging of C/C++ developers from FOSS finally begun?

I told you people this would happen.

>>61458027
now you just want to turn it on us

>>61457722
> Assembly
> 1s 0s
autism ™

>>61457847
Segmentation fault

>>61456733
please don't post degenerate anime characters in my board.

File: analog-communication.gif (961KB, 500x423px) Image search: [Google]

961KB, 500x423px

>>61457847
sigsegv
bus error
page fault
reference counting
cache lines
pointer math
into the wild
trial by fire
rebirth

mastery

caring about security vulnerabilities is extremely autistic

>>61456733
This is what is called sponsored article.

File: Screenshot_2017-07-20_00-53-59.png (133KB, 785x446px) Image search: [Google]

133KB, 785x446px

https://twitter.com/ryanhuber/status/877623129903738880?ref_src=twsrc^tfw&ref_url=https%3A%2F%2Ftechcrunch.com%2F2017%2F07%2F16%2Fdeath-to-c%2F

File: Screenshot_2017-07-20_00-55-23.png (158KB, 731x637px) Image search: [Google]

158KB, 731x637px

Why are fags so fucking dumb?

>>61456733
> rust
gas yourself

>>61456733
Does it pass tests on BSDs reliably?
No.
source: https://news.ycombinator.com/item?id=13889240
Is there a reason to give a shit about Rust for portable prorgams then?
No.

>>61467615
literally no reason to give a shit about non-OSX BSD for that matter

>>61467615
Isn't BSD dead?

>>61456733
Yes, let's use a language without a stable ABI for systems programming. That'll be great.

>>61457396
Wait ferris is a crab and a trap now??

...ok

Daily reminder + operator in rust might malloc whitout freeing, try to run hdparm on your storage or even send info about your system to some 3rd party server and you wouldn't know about it because rust is even less readable than perl.
Meanwhile the + operator in C is safe.

>>61456733
Is C the white cis male of programing languages?

File: Suzuya_scary_face.jpg (138KB, 1134x767px) Image search: [Google]

138KB, 1134x767px

best girl (male)

>decide to try rust in 2015
>download into wangblows VM
>huge MSI installer
>sees Mozilla logo and 3000 deps
Didn't make it past the installer agreement

Stupid FUD. Once you write low-level code, Rust is as unsafe as C (or even worse, because you have to redeclare all the prototypes yourself). If you only write high-level code, there's no reason to use Rust.

File: 1499597804103.gif (3MB, 573x523px) Image search: [Google]

3MB, 573x523px

>>61456733
>Mozilla products

>>61468702
Multiple best girls (male) can exist and can live in peace

>>61468674
Wtf?? Source? What are you smoking?

File: 1486561174186.gif (408KB, 400x264px) Image search: [Google]

408KB, 400x264px

>>61468919
Cute

>>61469006
>operation overloading

>>61456733
Rust:
>Adding support for the functional paradigm
>Better memory safety while maintaining performance.

Sounds like healthy design choices.
I imagine that C/C++ is alive because of
>Better support and tools
>Amount of experts in C/C++ >> Rust

If not for those two, why would anyone pick C/C++ over Rust?

>>61469188
Like you said, experience and legacy software.

File: 1500539735775.webm (904KB, 426x426px) Image search: [Google]

904KB, 426x426px

>>61468710
>wangblos
Found your problem :^)

>>61458111
There is literally no reason to port something that doesn't receive external input to a """safe""" language.

>>61469607
fucking cute, i'm 100% str8 and i'd still deepthroat that

>[C] gives its users far too much artillery with which to shoot their feet off
>Buffer overflows and dangling pointers lead to catastrophic security holes, again and again and again, just like yesteryear, just like all the years of yore.
So his complaint is that people are too stupid to do a simple bounds check or run their shit through a leak checker, and that "codebases with these languages always have security holes!" without neglecting to take into consideration that perhaps its because for the last 40 fucking years all the important shit has been written in these languages, which of course means they're going to have the highest rate of "big" security problems since they're the languages all the "big" shit was written in.

Or to summarize it: Programmers shouldn't be trusted to program
Rust is only good when you execute unsafe code anyways, making it a moot point.

>>61457890
>Rust wins in most benchmarks
But that's outright false?

>>61457890
fucking lemeo, compared to what language? swift? top zozzle my nozzle

>>61469188
>Sounds like healthy design choices.
They would be if every other design choice wasnt hand-picked from the bottom of the dumpster of "bad design paradigms" from every other language.
Also as most people have already said, in order to really make Rust as fast as it needs to be you have to disregard the safety anyways

Rust is a faggot language that nobody cares about. There are no jobs for it either.

>>61456733
>Tranny cat with tranny language

subtle

>>61457847
Teacher getting confused by his own pointer-pointer-pointer.
Oh and >>61464418, lots of this.

>>61467562
>>61467569
>lang
just say language for fucks sake, my ocd is having a hissyfit.

Daily reminder of the things written in C/C++:

All OSs desktop and mobile, and the new ones like Fuchsia.
All firmware on billions of embedded devices, from civilian applications to military.
Pretty much most of the scientific research software.
All performance critical software from simulations, CAD, rendering both photorealistic and real time like game engines.
The fucking INTERNET.
All security software, like encryption, firewalls etc.
All drivers.
All the good books that I've read on CS, networking, cybsec, only mention C and Linux, other languages and OSs don't even fucking exist.
Daily reminder that if you removed all the Java,C#,Rust,Go... code out there, not much would happen.
Daily reminder that if you removed all the C/C++ code, we would be back in the middle ages.
Daily reminder that only koders use Java,JS,C# and that they know nothing about CS.
Daily reminder that Rust,Go... are just fucking memes no serious programmer gives a shit about.
Daily reminder Rustfags care more about their crazy political ideologies and Rust is just a way for them to spread their filth.
Daily reminder that C/C++ will outlive you.
Daily reminder that koders like sucking dick.

File: 1491083943662.png (55KB, 211x269px) Image search: [Google]

55KB, 211x269px

>Daily reminder that koders like sucking dick.

File: ISTP.png (47KB, 828x493px) Image search: [Google]

47KB, 828x493px

>>61470154
Behold the world through the eyes of an ISTP

>>61467562
>writing code that doesn't buffer overflow is hard
Not really... You just need to use containers that do the checking for you, there's plenty of libraries that provide such containers. Also it's easy to design your library in such way that it never gives the user raw pointer.
Do these people think that just because the standard library doesn't provide vector implementation or input reader you have implement them yourself?

>>61470276
What you're saying is that you need to use C++ instead.

>>61470306
no sepples is almost as big of cluster fuck as rust.
Also in bigger projects sepplesfags implement the allocators and containers themself and at that point they might as well be using C.

>>61470276
>Do these people think that just because the standard library doesn't provide vector implementation or input reader you have implement them yourself?

Yes, they really are that stupid.

>>61470267

You sound upset.

https://www.viva64.com/en/b/0324/

>>61470331

C++ is preferable for bigger projects because of templates. Unfortunately most people don't really grasp their possibilities.

>>61470368
People overuse templates.
Just write C, but use STL for the containers that don't need to be optimized and RAII to avoid memory leaks and dangling pointers. Easy.

>>61470377
>>61470368
>no my way of writing sepples is the only correct way to write sepples
Biggest reason to not use sepples is that you don't have to deal with sepples programmers.

>>61470408
Use the features that are appropriate for the task at hand. Why does that statement trigger you?

>>61470377
>People overuse templates

You can say that about everything. Also, judging by the rest of your post I don't think you understand templates.

>>61470430
I'm talking about user-defined templates of course. Using standard library containers is a bit different.

What is it about rust?
Never tried it but every ((blog)) has comments that say "rewrite it in rust"
Is it a meme /g/?

>>61456733
sorry, i am not a nigger, lesbian, fag, sjw, or person of color, and i am not into politics, so rust is not for me

>>61470483
Hipsters love to jump on new technologies, you have the change of being the first one to blog about something making the actual blogging easy. Makes your profile look good if you can say that you have been there from the start and if you shill hard somebody might actually think you like the shit you are blogging about.
In case *it* becomes next big thing then somebody might hire you.

>>61456733
You can't program with memes anon

>>61470483

It's a political thing. The C/C++ community is very decentralized which makes it difficult for any one entity to impose its ideologies upon. By forcing people to use Rust they hope to change that.
There's no technical reason to use Rust. The benchmarks where Rust comes ahead are special cases designed specifically for advertising purposes. They're actually lying to people saying that you can write safe and faster than C code. Due to the number of koders around, a lot of people believe that since they don't know any better. The very fact that they lie to people like that tells you a lot about the Rust community.
Everytime I see some leftcuck suggest all the trillions of lines of C code should be rewritten in a meme language like Rust I chuckle.

>>61470408

You didn't understand my post did you?

>>61470822

>The C/C++ community is very decentralized which makes it difficult for any one entity to impose its ideologies upon.

Nice joke. Of course, only a moron who says "C/C++" would actually think that.

C++ pulled a classic embrace-extend-extinguish on the C community. It was fully backwards compatible with C but using any of the tempting C++ goodies like vectors would lead to an impenetrable ABI the likes of C would be locked out of. The second you use them, you're locked into C++. Using C++ begets more C++, a cycle that inevitably leads to the creation of ridiculous shit like boost.

>>61471837
>C++ pulled a classic embrace-extend-extinguish on the C community.
Funny how C was always more widely used than C++. C is still more widely used than C++.
>It was fully backwards compatible with C
Any nontrivial C program will fail to compile as C++ unless it was built specifically to work as C++ too. Nobody casts malloc unless they know the program is intended to be compiled as C++. It's even worse when you get to C99.
>using any of the tempting C++ goodies like vectors would lead to an impenetrable ABI the likes of C would be locked out of.
It's piss easy to expose a C interface in C++.

File: 13129702.jpg (11KB, 320x320px) Image search: [Google]

11KB, 320x320px

>>61469607
Stop turning me gay, faggot

>>61469607
Still would.

>>61456733
>numale webdev read about GOTO FAIL; incident
>WE NEED TO BAN C NOW!!!
Fucking retards.

>>61457801
>a language developed by a bunch of browser devs is beating over 30 years of concentrated autism
Ayyyy

>>61457383
Ha ha ha ha , commies working.

They are fucking idealists they don't need to work. In their mind they are already superior to you.

>>61471837
>only a moron who says "C/C++"

Nice argument.

>C++ pulled a classic embrace-extend-extinguish

C++ is a superset of C. Bjarne developed it a few offices away from Kernighan and Ritchie. Unsurprisingly they have a lot in common. If you knew anything about the language you'd know this but I guess talking out of your ass is easier.

>>61473806
>C++ is a superset of C.
*mallocs externally*

>>61471837

There is literally nothing wrong with vectors, maps, and other standard libraries.
Nothing.

>>61473496
keep working, wagecuck

>>61473924
>maps
std::map and std::unordered_map are fucking shit for efficiency

why is /g/ so /g/ay

jesus

>>61473948

std::map has log2(n) efficiency for lookup you autistic twat. Learn some math.

File: 1496796571553.png (252KB, 420x420px) Image search: [Google]

252KB, 420x420px

>>61457722
What kind of """Assembler""" is that?

>>61473816

Do you understand how supersets work?

>>61470049

>BUH I HAVE OCD

No you don't, stop saying that to try and sound cool.

By the way, shorthand is completely acceptable in an environment with a 140 character limit.

>>61458111
At least it has a respectable standard. Very few languages have that.

>>61474043
If C++ were really a superset of C, then all valid C programs would compile as C++.
This is not the case.

>>61456733

>Hoezilla wants programmers to start converting all code to Rust, especially C code
>FF is still written in C++
>Rust was written in C

I knew leftists were hypocrites but god damn this is to much to take.

>>61457847
use Clang to find out what's the problem exactly.
not kidding, it's useful.

gdb is also useful.
NetBeans / Code::Blocks also has nice debug features.
(it was, to me.)

>>61474063

But they do compile with a few exceptions.

>>61469861
[spoiler]u are 100% gay.[/spoiler]

>>61474157
>with a few exceptions.
Then it's not a superset.

>>61474157
>with a few exceptions
>>61474043
>Do you understand how supersets work?

>>61474171
>>61474177

You live in a very black and white world where you are either 100% something or you're 0%.

>>61474267
Mathematical terms like superset are black and white, that's the point.

>>61474267

Mathematical terms such as subsets, supersets, etc have very specific and rigorous definitions. You clearly haven't taken topology or even discrete math.

>>61474292
That still doesn't change the fact that Bjarne never used C++ to push for a political agenda. C++ features were so because of it's legacy to C not because of some political plot.
Now I have to go, I'll respond later if the thread is still here.

Newer C has a lot of cute little syntax things not supported by C++ compilers, often because there's a C++ solution that is meant to cover that case.

Though, in terms of raw features i.e. "C does this and C++ doesn't", I'm pretty sure there's nothing. It's just that the C++ way of writing it might be less concise.

>>61474447
C99 allows you to stack-allocate a variably sized array.

void demo(int n)
{
    int arr[n]; // not valid C++, but supported by many compiler extensions
}

There's variable array struct members too I guess.

>>61474484
Oh yeah, forgot that C++ doesn't do that exact thing. I guess the STL kinda covers that, though?

I haven't touched C++ in some time, it just makes it hard for me to reason about programs in general.

>>61474550
The C++ way to do it is to use a vector.

void demo(int n)
{
    std::vector<int> vec(n);
}

But that incurs a heap allocation so it's a lot less efficient, and it's not exactly the same thing. Kinda disappointing desu.

>>61474609
or alloca (which is super jank), I guess

>>61474658
only has function scope and won't call ctors/dtors, it's fucked

>Why are there always so many fucking rust shills whenever a C/rust thread appears?
It's called the Rust Evangelism Strike Force

>>61474130
They're writing a new browser in Rust, called Servo.

File: 4a45d4f9069f0ca5ecd5c5e41ed6ae60.png (1MB, 1066x1505px) Image search: [Google]

1MB, 1066x1505px

>>61474130
>>Rust was written in C
Um no, before becoming self-hosted it was written in OCaml.

>>61470154
And why are these things written in C/C++?
Because it's an old language.

>>61457722
Nice one Brianna