When will this meme die?

Probably less time than you think. Ten years from now everything real will still be C/C++. How long did it take Ruby to die?

>>105605258 (OP)
>>105605287
Just 2 more weeks

ripgrep is blazingly fast and fearless, it's basically over for binutils

>>105605258 (OP)
2 more weeks, trust the plan

Friendly reminder Unix troons had a literal "rewrite in C" campaign

>>105605650
that never happened there was just no software before c

>>105605258 (OP)
Probably never, it’s a genuinely good language or at least has good features, the syntax sucks and it’s ugly to read, the issue is rightoids completely give up cultural power willingly so trannies come in and co opt everything.

If right wingers could stop being retards and start participating in advancing society instead of being brainrotted by conservativism we could have nice things.

>>105605663
Yeah bro, computers did not exist before C.

Why do incels hate Rust when they don't even program?

>>105605868
why are trannies so annoying

>>105605921
Why do you jerk off to tranime?

>>105605258 (OP)
>>105605287
Rust is faster, safer, and easier to use than C/C++. Rust will replace C/C++ the same way C replaced B (which was easy because only 2 people ever used B and they were the same people who made C).

>>105605317
I try to avoid ripgrep, because the creator is a dick. And honestly, the speed difference with grep is imperceptible for my normal usage.
It's also not a drop-in replacement, different flags and default behaviors.

>>105605663
Why do you Russians lie so shamelessly? Is it the fetal alcohol syndrome?

>>105605932
cause it's hot?

>>105605961
Is this a janny or is poccnr living rent free

>>105606016
Then stop complaining about trannies and go back to Grindr, faggot.

while people complain about "syntax" and shit their pants due to borrow checking issues, I'm having a fucking great time with trivial dependency management, type-safe SQL queries, HTML generation with Maud, a great cryptographic base (RustCrypto), and set-in-stone error handling (with thiserror).

>>105606181
Import diesel, nigga

>>105606181
>trivial dependency management, a great cryptographic base, and set-in-stone error handling
What structures within crustacean culture lead everyone to using telemarketing terms like this?

>>105606247
experience. the terms are conjured when comparisons with other systems are made.

>>105606247
Corpo speak is a sign of employment. If you can't talk properly you will never get a job.

>>105605287
>How long did it take Ruby to die?
nigger, it is still going on strong sadly

t. employed by a company using ruby on its backend

>>105606291
*speak

>>105606291
>>105606295
I almost fumbled and said "anime is for trannies" to a co worker who had little tranime dolls on xer desktop at work.

>>105606273
It seems more likely to have been internalized while perusing the official site and documentation

>>105605258 (OP)
>I'm for sure not shilling Rust

>>105606371
Every Rust thread gets turned into a Rust shill thread.
How do they do it?

>>105606392
I just told you, dumb fuck

>>105606181
I get that you're baiting but all of that is easier with Go.

>>105605937
>Easier to use
Just wait until you want to do something concurrently.

>>105606490
no, I've written over 10k lines of Go:
- I prefer Rust's dependency management to Go.
- I have not done any SQL work with Go, but given the lack of Option, you simply will not achieve the same level of type safety.
- Go's `html/template` is shit compared to Maud.
- Go does not allow for 3rd-party hash algorithms. see https://github.com/golang/go/issues/69892
- Go's error handling is worse than Rust due to non-exhuastive pattern matching (in fact, pattern matching in general does not even exist in Go).

>>105606511
Sounds like you love all the functional shit in Rust. If that's the case then why are you using Rust's half baked type masturbation/functional features? If you're going to be retarded go full retard and use Haskell.

>>105605692
The proper right-wingers' response is to adopt Ada and expand its use cases and carefully add useful features.

>>105606517
Haskell's immutable data structures can result in memory bloat when serializing data to disk then reloading it. this is important for me and some of my work.
Haskell is also less stable than Rust. Rust allows me to do lower-level work than Haskell if needed.

>>105606511
>over 10k lines of Go
I probably wrote that in the last month.
>I prefer Rust's dependency management to Go
You're retarded. Rust dependency culture is exactly like that of npm, because most rust devs are webshitters. Every rust program needs dozens to hundreds of dependencies while Go has an anti-dependency culture.
>I have not done any SQL work with Go
>Go's `html/template` is shit compared to Maud
Aka you have no idea what you're talking about. Go has dozens of SQL drivers and builders and HTML template engines. I'm working on an imageboard that uses squirrel, pg (for postgresql) and quicktemplate. All you have to do to handle null queries is use one of the null struct types.
https://pkg.go.dev/database/sql#Null
Literally as simple as
var ip sql.NullString
>Go does not allow for 3rd-party hash algorithms
So I'm imagining importing github.com/matthewhartstonge/argon2?
>Go's error handling is worse than Rust due to non-exhuastive pattern matching
Unironically what is the usecase?
>pattern matching in general does not even exist in Go
Literally what? It has RE2 regex support.

>>105605258 (OP)
It’s already dying they don’t even a have a gui.

>>105606572
wdym they don't even have a gui nigga they literally have an entire OS and a DE

>>105606568
>I probably wrote that in the last month.
yes, Go is really good at increasing your LOC.
>Rust dependency culture is exactly like that of npm
I disagree, and even if I am wrong, I do not give a shit.
>https://pkg.go.dev/database/sql#Null
not pattern matched.
>So I'm imagining importing github.com/matthewhartstonge/argon2?
not a hash algorithm, hence it does not implement `crypto.Hash`.
>Unironically what is the usecase?
not forgetting to handle things, such as not forgetting to do `if !myNull.Valid {...}`.
>Literally what? It has RE2 regex support.
regex is not pattern matching.

>>105606572

>>105605258 (OP)
When they finally standardize a memory model.

>>105605948
I've always just used ag.

>>105605663
>the young earth C-ationist

>>105605663
Unix was written in assembly originally lol, and some basic programs like cat, and the assembler.

>>105606604
>yes, Go is really good at increasing your LOC
Maybe if you include test files and boilerplate error code.
>crypto.Hash
After reading the github issue, I agree with the official position that a fork is better for that guy's usecase. While more flexibility is nice, I understand not supporting it if increases maintenance burden, especially with all of the x/crypto libs going to merged to the core soon.
>not forgetting to handle things, such as not forgetting to do `if !myNull.Valid {...}`
And as much I loathe
if err != nil {return} boilerplate, I don't see the need for pattern matching. The only thing from rust I like is being able to handle basic errors with ?, and the Go team are stupid niggers for rejecting that. My backend LOC would probably decrease by 20% if that was standard.

>see a new shell (nushell) shilled
>it's written by a tranny, in rust
Why does this keep happening?

>>105606680
It's a fetal alcohol syndrome-addled Russkie. Fetal alcohol syndrome is associated with lying and confabulating (making something up and believing it's real, like how an AI hallucinates).

>>105606771
So a alcoslav confabulated something and therefore a troon made nushell? Interesting.

>>105606697
listen man, I enjoyed Go when I spent time with it. after learning Rust, internalizing the workings of the borrow checker, I absolutely prefer Rust, and will not be going back.
exhuastive pattern matching is just good. having access to macros when you need them is good. Rust gives me more options and more safety rails than Go, and that feels great.

>>105606548
The problem is that no one likes Ada.

>>105605961
not to be racist but lying is their culture how can you accuse them of lying thats russophobia

>>105606131
but I'm into anime women

>>105606753
They can't keep getting away with this

>>105606500
Coroutines in Rust are stackless. Yes, I have to go through Send + Sync bdsm, but at least they're usable everywhere. I've read lots of documentation pages about C++20 coroutines and I still have no idea how they're supposed to work. Sometimes they allocate, sometimes they don't, just deal with it

>>105606753
Rust has pattern matching, mature async/await along with stackless coroutines, static and dynamic polymorphism, templates, lambdas, AST-based macros, borrow-checking and allows you to drop into raw pointers and assembly the moment you're bored. All that while being 10x less bloated than C++ and faster than C when it comes to idiomatic code. It also attracts lots of (male) girls. The choice is obvious.

>>105606597
> Immediate mode gui
> no 3d
Ngmi

>>105605937
Rust is easier than idiomatic, correct C++, but it's definitely way more difficult than C.

>>105606500
Thanks to Send/Sync, tunnels and wrapping mutexes thread based concurrency very easy. Async can be more tricky if you insist on zero cost.

>>105605663
Lisp machines are the past and are still the future

>>105605937
>Rust is faster, safer, and easier to use than C
rust has been created with incompetents in mind
so if you are one, yes you will find it easier to use

>>105606181
>trivial dependency management,
You really don't have this. Dependency management is really something like what java did with modules. rust crates are barely an evolution over what C did, to be honest.

>>105612406
>rust crates are barely an evolution over what C did, to be honest.
imagine getting filtered by deps
yes its a chore
but once you get your environment down, you just dont think about it
and to be honest
wtf do you even need to be doing to even encounter that as a problem?

>>105612417
It's telling that the only thing Rust pozzlords can do is dunk on a 60 year old language.

>>105612427
the funniest part is that the grand vast majority of times their critique just bounces
and in effect they out themselves as incompetents

>>105612365
>rust has been created with incompetents in mind
The Rustchad definition of "incompetents" is "expert C/C++ programmers." Rustchads are so good at programming that the best C and C++ programmers in the world are incompetent next to them.

>>105612443
Pointers were invented by "mathfags." Pointers didn't come from C. Your fetal alcohol syndrome is acting up again.

>>105612463
but nobody cares abt crabs doe
except for reddit

>>105612475
im sorry not fetal
its ACQUIRED alcohol syndrome
its not the same, dont insult my parents

also that was a joke you fucken dweeb
buy yourself a sense of humour

>>105612417
Is this because rust developers don't have experience with other languages? Rust doesn't have a true dependency management system. You can't decouple your dependencies from your code with rust crates. In java this is just
module a.b.c {
requires a.b.c;
provides a.b.c.InterfaceName with a.b.c.ImplementorProxy;
}

module my.stuff.foo {
requires a.b.c;
uses a.b.c.InterfaceName;
}

and then in your application you can do
InterfaceName blahProxy = ServiceLoader.load(InterfaceName.class);
blahProxy.specifyDetails(...);

Where the proxy isn't even needed, but if you had multiple providers (maybe multiple methods of doing authentication is an example) you could benefit from using one. Rust crates aren't really different than say, pythons requirements.txt. Better than C for sure but it's not like that's a difficult thing to achieve.

>>105612603
i think its a webshitter thing
straight and honest

i do fintech but all i need is my opencl deps
i mess around with opengl but sdl deps aing hard to get either
wtf one has to do to really find themselves in dependency hell?
as in a needs version z of b but then c needs version y???
what the fuck?
if youre not doing arts and crafts tier webshittery you just dont encounter that problem
what the fuck?

>>105605258 (OP)
When something manages to provide its same benefits with fewer drawbacks

>>105612365
>rust has been created with incompetents in mind
That's literally Go.
Rust literally goes the opposite way, striving for perfection no matter how much cognitive load it entrails.

>>105612700
>striving for perfection no matter how much cognitive load it entrails.
but thats literally a childproofed language
if youre confident in what you do
you dont need the garish tape everywhere and safety pins on every single button

im sorry
but rust making it 'impossible to shoot yourself in the foot at the cost of cognitive burden' is literally a lang geared towards people who cannot deal with their task, unassisted

even c itself is assisted as all fuck to be honest
to such an extent theres a class of information i just dont bother with, only delegate it to the compiler (types. i really dont fucking bother with em and sometimes i use a deliberately wrong type bc getting a compiler warning is faster than traversing the headers)

>>105612750
>but thats literally a childproofed language
>if youre confident in what you do
>you dont need the garish tape everywhere and safety pins on every single button
We have a real comedian over here.

>>105612750
>childproofed language
Rust has very steep learning curve. It's not a good language for beginners.

>you dont need the garish tape everywhere and safety pins on every single button
Tell that to people using static analyzers. Rust functions basically like C++ with one bolted on top.

>>105612773
>sad homonem
wheres your techni cal argumentation, crab
represent for your team, no?
you fukken dweeb

>>105612784
>Rust has very steep learning curve. It's not a good language for beginners.
c is the best beginners language, but crabs use rust bc they cant deal with it
this is a stupid metric

>Tell that to people using static analyzers. Rust functions basically like C++ with one bolted on top.
the difference is that you have to do concessions in your code as in: more rules than in C
rust is not an upgrade
its a sidegrade at best

unless were talking about sepples
sepples is cancer. and they are your target, not C.
c offers things that are the antithesis of rust
namely:
no safety mechanisms
thats one of the major selling points of C.
you wont be able to outsell it by negating one of its major selling points

>>105605317
same with fd-find. a lot of the rewrites are pretty good honestly.

>>105605948
>>the speed difference with grep is imperceptible
>he never did grep -R v rg comparisons
kek

>>105612817
>c is the best beginners language, but crabs use rust bc they
C is commonly recommended for starters for people who want to get into Rust.

>the difference is that you have to do concessions in your code
So you do when working with static analyzers.

>>105612857
>So you do when working with static analyzers.
completely wrong
>C is commonly recommended for starters for people who want to get into Rust.
exactly because nothing holds your hand
except the type checking
and theres little to no abstractions
or rather
the abstractions are at the perfect level where the notable individual operations of a computer are evident, but without having to really get in deep into the details

but thats EXACTLY what makes C a difficult language to work with when dealing with a bigger project
but when youre good enough to define your framework
including the syntax
nothing compares to c

do we really need to compare what it takes to make a double linked list bw our languages again?
you know how things are
*i* know how things are
why do you keep returning to the same talking points?

>>105612700
>Rust literally goes the opposite way, striving for perfection no matter how much cognitive load it entrails.
This may be the mantra but it's not necessary. Ada/Spark is not worse than Rust on guarantees it can make but it does so in a way that's easy to understand and intuitive for a developer. I guess it makes rust developers feel better about themselves though.

>>105612603
Rust isn't some high level OO shitlang like Java. What you're asking for is retarded.

>>105612907
>Ada/Spark is not worse than Rust on guarantees it can make but it does so in a way that's easy to understand and intuitive for a developer
and yet no one actually uses it unless contractually obligated to... curious......

>>105612907
Ada spark can't safety free dynamic memory. It took Rust for them to come up with some limited support for this.
Ada also doesn't strive for zero cost. Rust is a systems programming language and it tries to be as fast and safe as possible, that's what I meant by perfection.

>>105612918
I don't understand his code. Isn't he asking for just re-exports? Rust can do this

>>105612930
Lack of Ada popularity is probably due to its shitty licensing early on. But you can't really say that no one uses it. It has its uses in legacy safety critical systems.

>>105612904
>the abstractions are at the perfect level where the notable individual operations of a computer are evident, but without having to really get in deep into the details
It's the same as Pascal, FORTRAN, and a lot of other languages from that time period and older.

>but thats EXACTLY what makes C a difficult language to work with when dealing with a bigger project
C is a difficult language because of the weak design of everything. Basic features don't work and it's full of defects.

>>105613001
>I don't understand his code. Isn't he asking for just re-exports? Rust can do this
pretty sure he's just talking about exporting concrete implementations of interfaces defined elsewhere..... I think.

Ironically, he can probably do what he wants with crate / stdlib traits and implementing them for his crate(tm). but whatever. I don't know why people ask why they can't do stupid shit in a language that's basically C++. obviously a lot of dynamism is just not possible.

>>105613001
>legacy safety critical systems.
ya... contractually obligated*

>>105613097
>pretty sure he's just talking about exporting concrete implementations of interfaces defined elsewhere.....
So, pub use whatever::path::op as fag ?

>>105613053
>Basic features don't work and it's full of defects.
theres very few defects

what you meant is that its defectuous within your mental framework
but youre not the center of the world
and CUDA, as well as opencl is C

you know why?
because there exist people who can keep their ducks in a row wo assistance
and these people are a superset of people who can write gpgpu
ergo:
rust is a jeetlang. theres a competence barrier to use C effectively in a pro setting
and C will always remain the norm bc you can do C before you can be trusted with custom HW
on t he flip side, nobody is gonna bother implementing rust when c will do

>>105613123
idk man. idk anymore I give up. I've seen so much java jeet cancer I think it's a feature at this point if it isn't like java.

dependency injection is gay.
I hate classloader autism.
I just hate the whole ecosystem.

static TRVTH is better.

>>105613151
this sounds like a declaration of allegiance to c
but c can be a cruel mistress
high level shit does have its usecases

>>105613211
high-level in this case means trait objects or basically vtable laden fat pointer slop.

this is fine in Java, fine even in some cases in Rust, but realistically, Rust not being built around that concept is sanity.

>>105613220
thats what i was saying, too
theres a context to things
and if a specific feature makes it easier to accomplish the mission
then you should go with the tool that provides it
doesnt mean one needs to turn their code into a demo of the language capabilities either, kek

>>105613220
>>105613246
(cont)
in fact, you could mimick everything using vanilla C
yes, even the features of rust
but that would come at a runtime cost, making it- useless
*
that something can be done, it doesnt mean it has to be done that way
you COULD use a sharpened crowbar to drive screws
but why??? take a fucking screwdriver ffs

t. has 500klocs of C under his belt btw
i sometimes do use C instead of shell bc its easier for me.
mostly bc i dont have 500k locs of shell, but it still gives an idea how fluent am i in c

and i code c on x 86-64
i believe its more complicated than writing for embedded to be honest
the machine youre writing for is more complex, thats what makes the process- more complex
i think
i never coded for embedded to be honest

>>105613274
>in fact, you could mimick everything using vanilla C
>yes, even the features of rust
It's the other way around. You can do everything C can do in Rust. You can't mimic anything with C because C is too weak.

>>105613393
with runtime?
you can do everything
maybe rust is more expressive than c
but c is more straightforward
the no red tape policy kind of thing

i love c bc its simplified as far as it can be
thats the fukken reason
i like my things simple
they can be extensive
and thats where most people fail
but i like em simple

pure fukken nature barrier
if you dont have the ram in your brain to modelize a whole system
youre not gonna be good in c
----
however you look at it
c-ultists are the elite
and all the derivatives exist to pretend to follow us
yes theres plenty posers
but thats where our "elitism" comes in
except we give you the tools to join us
but you lack intellectual rigor
and you end up failing, then saying "youre elitists"
its not that
its just that theres a barrier of entry to do a good job in C
bc, like stated
theres nothing to hold your hand
except the types
so dont use void * unless it matters
bc thats the equivalent of detaching the carabiner from your only lifeline

>need to do something at compile time
>HELP ME SED-SAMA HEEEEEEEEELP
Absolute meme of a programing language.

>>105613469
>c-ultists are the elite
>and all the derivatives exist to pretend to follow us
>yes theres plenty posers
C didn't invent or create anything. C is the derivative. C is the poser.

>>105613563
you can extend c wo a problem
exactly bc its such a simple language

truth defends itself
C is ace however you look at it
->its not without reason we still use a 60 fucking years old language lamao

>>105613590
>hater talk
c is the upgrade
did you do basic?
you didnt
or you would understand the goto and NEVER would you have uttered the sequence of words "clean code"

>>105613593
>you can extend c wo a problem
>a simple language
So simple we had to curse the world with autotools.

>>105613593
>you can extend c wo a problem
You can't extend C at all.

>->its not without reason we still use a 60 fucking years old language lamao
Fortran, COBOL, and Lisp are still used because they're good. C is still used because the people who made it are aggressive shills and bad people.

>>105613632
>the whole industry being retarded
that would be a shocking first, wouldnt it?
>>105613634
>You can't extend C at all.
what?
you cant pre shell and even substitute?
did you EVER , even ONCE in your life used a makefile?

>hurr durr old scarred veteran
if thats what i am
then you better get your ack toegether

>>105613593
>you can extend c wo a problem
>exactly bc its such a simple language
No you can't.
This is why embedded people often use languages that compile to C instead of writing it themselves.
And why people use code generators like Bison instead of encoding it directly in the language, like you could with Lisp.
Also why people have to use Makefiles with xxd instead of being able to compute it at compile time.
The C Preprocessor is just barely capable enough to make things like tree.h, but it's annoying to use.

>>105613654
>you cant pre shell and even substitute?
>did you EVER , even ONCE in your life used a makefile?
None of that is extending C.

>>105613672
youre retarded
and they are retarded
and the people you quote are also retarded even if i repeat myself
>fucking sed is not a thing
completely utterly and entirely retarded
>white
no, you are not
a fucking syrian is whiter than you

>>105613672
>tree.h
cursed.

>>105613687
retard
>modifying the code before compiling it is not extending c
retard
i mean like
complete fucking aphantasia levels of retard

>>105613697
no, he's absolutely right.
I've worked on projects exactly like he's talking about. Some fag wrote a DSL using XML documents and a perl script that shits out C code for a lot of tedious shit that most modern languages can do with basic meta programming and templates.

keep coping though, shitter.

>>105613712
>extending c is indeed possible
>but its not
>cope, shitter

your own incompetent does better than you
how should we call you, then?
i want you to say it

>>105613469
Rust uses c runtime

>>105613707
>>modifying the code before compiling it is not extending c
It's not. That's the definition of not extending it. Are you trolling or did the fetal alcohol syndrome affect your brain that much? Your brain probably looks like Swiss cheese.

>>105613722

>>105613724
>the difference is that you didnt make it into a gcc plugin

the absolute fucking state of crabs...

>>105613721
>>extending c is indeed possible
>>but its not
>>cope, shitter
That's not extending C. Writing another program that generates code is not extending a language. You can literally do that with any language in the world too, so that's nothing special about C. You can have a program that turns Haskell into Brainfuck but that doesn't mean you're extending Brainfuck.

>>105613748
The nice thing about extensible languages is that you don't need to write compiler plugins to extend the language.
You could not make something like safe-math-rs in C
https://github.com/GotenJBZ/safe-math-rs
I'm not that anon, by the way.

>>105613782
>>>but its not
how when it is?
just change the source before you compile
->the crab cannot possibly comprehend that
and thats why you use rust, lamao

>>105613786
yes you could
you are unironically retarded
you like to rave abt your abstract ions and such
->cant manipulate actual mental abstractions
ill walk you threough
and youll see how fucking retarded that is
and how motherfucking, utterly fucking botttom of the barrel retarded you are

->how bout just generating code
->you can have an arbitrary framework around that bc your whole language is an abstraction

and if you cant understand that
im sorry
youre just too fucking retarded then
like literally
you fucking lack IQ
hard fucking compute power in your brain

>>105613821
So your solution is to stop using C? I agree, that's the best solution.

>>105613798
>how when it is?
>just change the source before you compile
That's not extending a language and has nothing to do with C. C really dumbs people down.

Just 2 more weeks, trust the plan

>>105613843
no
my solution is that YOU stop using C
*small *fukken *nuances *TM *LMAO (also TM)

>>105613821
>->how bout just generating code
>->you can have an arbitrary framework around that bc your whole language is an abstraction
That's called using a compiler but you can do something even better and cut C out entirely. Instead of generating C, you can just generate machine code or assembly.

>>105613854
>t. seething
you can t do the same with roost
but not bc its roost
its bc youre retarded
>inb4
uh-huh, thats what

>>105613880
no
thats you being calles a solipsistic retard
and also the reason autists are trash
bc of a lack of mental flexibility ofc, what did you think about?

>>105605258 (OP)
When Microsoft gives up on it.

Problem is, big corporations don't like to admit when they make mistakes, see Boeing, diversity and plane crashes as an example of how bad they have to fuck up before pulling back.

>>105605287
I heard the same thing in 2015 when Rust was released. Except now my shell, me terminal emulator, my code editor etc are written in Rust.

>>105613892
You’re forgetting Amazon, Cloudflare, Discord etc

>>105613891
>thats you being calles a solipsistic retard
>and also the reason autists are trash
>bc of a lack of mental flexibility ofc, what did you think about?
You must be confusing this thread with your autobiography. C programmers like you lack mental flexibility. You can't understand what it means to extend a language because C can't do it, so you pretend they are actually saying something else.

>>105612059
The problem with Rusts concurrency model is that the borrow checker limits what you can do in parallel. Lets say you have a 2d grid, represented as a 1d grid to be more cache efficient, in most languages sectioning off ranges of that grid for threads to be in control of editing is trivial and it is safe as the programmer has restricted what data the threads can touch to ensure no data races. In Rust this is impossible as the borrow checker doesn't allow multiple mutable access to the same resource. As a result you either have to stick to single threaded accesses or spend more time creating copies of sections of the data, feeding that data to the threads and spend extra time forming that data into the shape you want after the work is done. It's additional overhead and work that doesn't exist anywhere else. This is a big problem for stuff like game dev where these sort of patterns are common and the extra overhead is not an acceptable cost (which is why Rust game dev seems to be DOA imo).

>>105613936
He’s not a programmer, he’s some kind of a plumber.

>>105613936
>no, u
>but elaborated on, this time
post busssy fgt lamao
ur a fckn retard
like, a 5 y o will bhreak you the fuck up

>>105613941
NTA but do you really retain cache locality if you are working from seperate threads

>>105613925
C shills:
>shill every day
>make 1000s of images of "Rust trannies" and people killing themselves
>make 1000s of insulting Rust logos like bloody scissors and poop emoji in the Rust gear
>make 1000s of homosexual "C chad" images
>lie and say C is the first programming language
>lie and say every language is based on C
>lie and say Rust has a backdoor
>whine about Rust's lack of an ISO standard while treating the C standard like toilet paper
>misunderstand what basic terms like extension and compiler mean
>make intentionally fake comparisons like different Fibonacci algorithms to pretend Rust is slower
Rust chads:
>do nothing
>win

>>105614002
except
<exhibit a
>20x C (not sepples) jobs as rust jobs

how does it feel to be a delusional retard?
does it hurt?
does your low iq make it worse?

>>105614002
99% of C shills don’t actually program. Ever wonder why the C help threads are always filled with beginner level K&R exercise questions?

>>105614015
Yet you are a jobless cnile. Embarrassing.

>>105614022
>le c shills
>all i see is rust shilling

how to rustNIGGER 101:
take what you see
say the exact opposite

would that make a rustpost automatically trolling outside of b?

>>105614034
>how to rustnigger 101...
pathetic

>>105614048
Truth hurts, doesn’t it

>>105614055
idk you tell me

>>105613941
>In Rust this is impossible

>>105614074
its a niggerlang

>>105613914
TBF can't wait for COSMIC to release. With the new Wayland protocol released, there is a chance they will implement the frosted glass effect natively.

>>105613986
you do in languages for competent progarmmers

>>105614083
>says something incorrect
>gets proven wrong
>*autistic screeching*

>>105614094
yeah thats you
also why do you disrupt the fucking discussion you trany fagot
also why is it always the self inserting tranies?

being transgender should be a bannable offence on /g/

>>105614089
>my choice in language magically brings cache locality from a separate threads
Why don't you go back to cleaning shit pipes you subliterate nocoder plumber faggot? I was not talking to you.

>>105614103

>>105614112
>t. trains

>>105614119
>reddit meme
kys w/a brick you fucking subhuman lamao

>>105614127
>kys w/a brick you fucking subhuman lamao

Cniles seething so hard this thread is going to stay at page 1 constantly before reaching bump limit KEK

>>105614119
>>105614127
(cont)
>derivative of a derivative
you absolute fucking nothingness
commit sudoku
itll stop the pain of you existing
things will never get better
you will always be this lame
you will always sleep on the couch
you will never propagate your genes (which is a good thing, just bc youre white doesnt mean you have value. in fact, were better off w/o your genes)

>>105614137
>basedduel
i thought youre a trany
and your basedduel is not convincing
another submission on your behalf
go suck tyrone maybe that will make you feel better
useful at least
thats what you usually do, no?

>>105614150
>>105614163
Wrong. Seethe :)

average rust user

>>105614174
i dont think im wrong
you worship niggers
you literally worship em
when i fuck nigresses bc they dont like they men

your söyciety is wrong
idk whats wrong with your men
but we aint like that
idk its the water or fukken microplastics or something

>>105614197
nah you're just seething LUL

>>105614207
seething abt what?
i did fuck 2 jewesses in my life
one was really filthy
but thats not technological at all
or so jany told me, and i agree to be honest

>>105614209
>>105614217
also trains
trains are always based

thread over

>>105614220
You are seething about Rust

>>105614241
just fukken pay hookers, lads
and if theyre illegal in your country
fukken go to holland
ur not poor, right?

>>105614074
This looks like it's creating a new array every iteration and not editing the original in place. So you're not doing what he asked and mutate the original array in place. So this is doing extra work over every other known language because it's creating a copy every iteration. This would crash performance in a hot loop.

>>105614258
It's not creating a new array. NTA.

>>105614258
>This looks like it's creating a new array every iteration and not editing the original in place
What, where? The only array here is [0; 64] buffer and you can clearly see it got mutated at the end.

>>105614244
no i just like to bulli crabs with my big, vast, and expansive brain
bc theyre assholes

note how you will never find me berating jai, go or zig threads

>>105614269
how, rust is functional

>>105614278
Yeah because Rust triggers cniles :)

>>105614244
in fact
go used the muscle meme for the gopher so theyre good guys
C-ultists should have a smidge of sympathy towards gophers
they use our imagery after all
thats a bridge if i ever saw one...

>>105614280
https://doc.rust-lang.org/src/core/slice/iter.rs.html#1666
chunks_mut does not create a new array

>>105614265
>chunk.fill()
#[doc(alias = "memset")]
#[stable(feature = "slice_fill", since = "1.50.0")]
pub fn fill(&mut self, value: T)
where
T: Clone,
{
specialize::SpecFill::spec_fill(self, value);
}

It's copying elements from the original array.

>>105614287
>triggering cniles
>>105614015
im ok with that
lamao

>>105614280
Rust is systems programming language with functional features.

What this code does is create a buffer, then split it into 4-length mutable slices and pass them into scoped threads. The scope borrows entire buffer and each thread gets access to some part of it. Once the scope ends, main thread waits for all of them to end at the end of their scope so it can use buffer again to print it.

>>105614300
Not really, it fills a slice with a given value.
Also, it's the supposed "work" that is to be done in a separate thread.

>>105614300
fill fills a slice with some value. in this example, it's the sequential id of the threads. wtf are you talking about

>>105614300
I'm curious what the OOP vs DOD programs are for the pictured implementations of Conway's game of life.

>>105614313
>>105614321
>>105614323
imagine attempting to maintain a narrative on g of all places
fukken lamao

every thread is a c thread in disguise
have fun <3

>>105614334
Who told you to leave, cnile? I need you to bump this thread into bump limit.


Rust is the most powerful programming language

>>105614300
>GPU: 9001 FPS

>>105614321
>>105614323
The documentation of fill says it creates a new slice by CLONING the passed element. I think I'm going to trust that over you guys.
https://doc.rust-lang.org/std/primitive.slice.html#method.fill

>>105614348
>aha i ackshually foresaw you all along
ok
did you foresaw i was gonna call you a faggot too?
btw
>imagine using a frog when youre a trany

>>105614353
>Ctrl F
>create a new slice
>0 hits

>>105614364
Wrong, keep seething :)

>>105614377
i think its right actually
and if i were seething i would have closed the tab LAmao

>>105614353
It is a memset.

>>105614386
You sure?

>>105614368
So you're cloning into nothing in that example? Stop avoiding the point. Are you or are you not doing extra copies/allocations over just iterating in place (which you can do in every other language), yes/no.

>>105614397
yeah
i legit dont give a fuck about you
shocker, i know

>>105614353
[T]::fill(self, value: T)
>Fills self with elements by cloning value.
>creates a new slice

>>105614404
Cloning into a slice. Where did you find it creates a new array

>>105614407
I don't believe u xD

>>105614300
>> #[doc(alias = "memset")]
Hmm

>>105614397
>>105614407
fyi the only people i give a fuck about are
-registryfag
-high iq tranimeposter
thts it
and you shartyhomos are, well, homos
so yeah
idc youre their admin
youre just another anon
and a disagreeable one at that

do some thing memorable, you then wont be a no-name for me

>>105614404
Copies of the element to be set into the slice blocks, not the fucking slice itself you dumdum

>>105614404
The only thing copied here is the thread number that's the chunk get filled with. It's the example work such thread could do. No extra arrays get created or merged. It just spawns bunch of threads, each filling some part of the buffer with sequential id number. Stop pretending to be retarded.

>>105614445
aaaaand
sory sory sory
theres fukken icelander
hes based
he makes tranies seethe

>>105614300
There is no return type. Where does the supposed newly created slice go?

>>105614397
>do some thing memorable, you then wont be a no-name for me
and by something memorable i mean show your expertise
i used to be a retard
but i improved my art
and now im a namefag without using a name
fukken
represent, fgt
represent the sharty, show expertise

>>105614287
What's the reason for this phenomenon? No other C/++ killers get the same response as Rust.
I think the Rust marketing team is absolute fucking genius. By taking a slightly left political views, they turned chuds into 24/7 unpaid shilling machines. Real 4D chess move kek

>>105614506
Well Rust brings something novel to the table, languages like zig or hare do not. Big corporations saw this and started replacing their old codebases with Rust.
This triggers the cnile

>>105614534
corpo saw consolidated interfacing bc thats what makes the difference bw the code-rhesus and the brogrammer
thers those who create interfaces
and theres the people who learn em

>>105614534
>>105614546
(and thats why you shpouldnt leave ihnterfacing to a fciking autisy btw bc they can into ergonomics.
bc they dont care, duh)

>>105614546
>>105614559
Are you having a stroke?

>>105614565
no, im just mildly drunk (only mildly bc i didnt get b& yet}
also try to keep up, slowie
i can be patient
b ut im also drunk so my patience can be cut irationally short

>>105614506
>By taking a slightly left political views, they turned chuds into 24/7 unpaid shilling machines.
Real

>>105605258 (OP)
When every human is born to its fitting gender.

>>105614622
then why do homos are never born as such?
ive looked into things bc being a homo is kinda wtf

they all either get raped or start with the question "why not?"

>>105614622
ive even squatted a trany discord
from the disc ussions:
a) tranies long for masculine feats
like fighting and such
and theyre evil and they dont care

idc either
they willingly hurt other people
and they just dont fucking care

>>105614640
They do? My sister is a lesbian, has had crushes on girls since elementary school, has never been with a guy (she did go on one date in middle school with a boy but got uncomfortable and left).
It's real, people are born homosexual.

>>105614640
>why do homos are
Being a faggot is a choice that can be rectified, but your rancid third world genes are incurable.

>>105614674
there isnt such a thing as 100% lesbian
ALL girls kiss girls
ALL girls also hear the call of nature
>>105614675
>esl
actually e4l
and how many languages do YOU speak, residue of a failed condom?

>>105614691
>there isnt such a thing as 100% lesbian
>ALL girls kiss girls
If that's true, then that means that there's no such thing as a 100% straight woman. That doesn't imply that there aren't women who only like women.
Also I just gave you an example of a 100% lesbian you dumbass.

>>105614706
it is true
its just that you dont present desirable traits
literally a you problem

>>105614710
>its just that you dont present desirable traits
Lol that you're implying I should want my sister to desire me

>>105614706
>>105614710
ok ill be nice this time

femfems are walking incubators
they select for desirable traits
they need security for the family and thats why they pick niggers
BUT
a white man is way stabler than, a nigger
understand this simple truth
become the master of your reality
and every woman will be yours
la tino, nigress, or white

bc theyre fukken walking, talking incubators
and if you pull the right strings they can only open legs

RTFM you dweeb

>>105614730
>and every woman will be yours
Including my lesbian sister, wow, thanks for the incest advice anon

>ESL admits to being a rape golem
kek but also grim

>>105614721
>>105614730
you need to emanate willpower
whot tf cares your sis becomes wet for you you aint gonna fuck her
shes a woman
if youre doing your job well ALL women will be wet for you
and thats why we despise fukke n motherfuckers, right?
you fukken dweeb
imagine needing g of all places to tell you abhout the fukken bees and the fukken flowers, right?

>>105614738
>>105614745
>implying femoids have a will of their own
eternal virgins
thats what makes men of us
that femoids can trust us to lead them NOT to do dumb shit

ehrm
i meant
>implying femoids have a will of their own
eternal virgins
---
what makes men of us
is that that femoids can trust us to lead them NOT to do dumb shit

ESL struck again...

notice how Cniles never post code. this point is the strongest of all, and nocoders or newcoders will glance over it.
you really do not know shit if you cannot post even a single sample of code.

When the USAID money runs out.

>>105614814
i post code whenever asked to
and sometimes just for keks

but notice, how
fukken crabs
NEVER EVER can demonstrate what they mean, in code

picrel is around makes my atoi ~3x faster than libc btw
goes to show what youre benchmarking against lamao
its also years old code theres so much wreong with it
yet
you barely approach what it was benchmarked agaist

fukken
crab ,soup is tasty

>>105605937
Meds.

>>105612846
>He replied to a qualified statement with something completely unrelated
kek

>crabs cant comprehend BARELY o ptimized code
>talk shit abt your codebase
learn to code you fucking brownoids

>>105614847
USAID money can't help with the C shill's fetal alcohol syndrome.

>>105613891
midwit tier bait.

>>105614946
yet you t ook it
swallowed it, even

>>105605258 (OP)
who cares? over 10 years of shilling, and it's still barely a blip on the radar. it's nowhere, and it's going nowhere.

>>105614973
>who cares? over 10 years of shilling, and it's still barely a blip on the radar. it's nowhere, and it's going nowhere.
C has over 40 years of shilling.

>>105605258 (OP)
It already is. Moving on to the next meme (Zig)

>>105614912
post something useful, not the same screenshot I saw months ago

>>105614982
lurk /dpt/ and /chad/ then
i did post how to have generics in c
i did post a practical application of sepples-like name mangling
i did post practical examples of divide to conquer through forcer inlines
i even presented a way to modernize c strings in a way thats compatible with the libc

WHO THE FUCK ARE YOU TO SAY I DIDNT DO NOTHING?
WHAT DID YOU DO YOURSELF, DWEEB FUKKEN NIGGER?

>>105614912
>crabs NEVER EVER can demonstrate what they mean, in code
You're ignoring how anons have been arguing over >>105614074 for a third of the thread

>>105612365
Fuck kikes.

>>105615034
ngl
im assuming
if im wrong thats ok
it changes things from 100% of crabs be ing rotten to only 99%
im ok with that
the amount of abuse ive heard from crabs justifies a way more brutal bias against them
even merely itt
f uck crabs
theyre salty whores who want to destroy everything

>not everyone is like that
yeah no
id rather sacrifice 1 potantial innocent if i were to destroy 100 demons than to let 1 innocent go
and alongside him have 99 demons go loose

im sory bro
rust is whoilesale cancer
you shouldnt be defending it either
they dont want to fix the cargoshit mess
they dont wanty tro extend the standard lib
and if you tell me
>just trust randos shit they found under a bench
yeah, im sorry
youre part of the retardation problem and should get the fuck back to r*ddit with the rest of the fucking retards
>yeah no just audit gorilions of lines of rec ursive dependencies
no
fuck off back to your sandbox

>>105606548
>Ada
Oh boy, it's gonna be great any second now. Oh, wait, they already fucked it up over three decades ago.

rust is better because there's only one rust
meanwhile C was downgraded from C99 to C11 only recently bumped to C23
just a small 12 points upgrade wth!

>>105615136
>rust is betta bc theres only one rust
no
and even if it was the case
>need something sligh tly diffferent
>oops chud, i guess you get fucked bc theres only one rust

>>105615091
>the amount of abuse ive heard from crabs justifies a way more brutal bias against them
C programmers are trying to trick people into using C because they know it's bad, so they can have more buggy software to exploit. Rustchads are trying to help people. That makes Rust better.

>they dont wanty tro extend the standard lib
What's there to extend? It's already better than C and C++.

>>105614973
Yeah if that was the case Rust threads wouldn’t be guaranteed page 1 with 300+ replies.
I don’t see that happening for zig or D threads.

>>105615091
Nothing to do with what I said but alright

>>105615181
That’s because cniles are offended very easily

>>105615181
it's just /g/ folklore.

>>105615181
See >>105614506

>>105615164
>C programmers are trying to trick people into using C because they know it's bad
cope
lamao
and projection like a dumb piece of shit
>>105615189
concession accepted

>>105606517
>sounds like you like doing stuff with your arms, so why won't you cut off your legs?
All single abstraction languages are academic wankery that will never take off
>everything is an object!
>everything is a list!
>everything is a function!
>everything is a logic statement!
>everything is an expression!
>everything is a stack!
>everything is a queue!
These are great for research purposes, "how would this be solved if everything had to be X" leads to new, possibly better solutions. For real usage however, a language that can only do the abstraction that's best at X is useless when you can just use one that also can do the abstractions best for Y and Z

I also reject the notion that monadic types such as Result or Maybe are a purely the result of functional languages
Yes, functional needed a black box abstraction that can be changed but not inspected, to shove any non-deterministic data into to keep their functions "pure"
But the exact same idea pops up in OOP. You have a shared interface/ancestor (eg. Result), with possible descendants (variants), but you don't know which it is which due to encapsulation (monad context), so you pass it an object that can handle every case and it's interacted with based on the first object's state. That's the visitor type. It's the same solution, but to a different problem, with type and inheritance replacing values
Even in structured programming. A function that takes X requires an X to be called. The scope of the function enforces the validity of X for it's duration. Something like "if let" and pattern matching are the more modern ways to solve this category of problem in a structured programming way (variant resolution tied to scope)

Rust will find it's niche due to it's safeguards.

C will stay alive in the embedded and as a library intermediary.

Go might take on C++.

>>105610127
>he doesn't know about Bevy game engine
>he doesn't know about GTK bindings
>he doesn't know about Tauri native web engine
come the fuck on retard

>>105605937
>faster
wrong
>safer
marginally, and the difference is insignificant if you take even the smallest measures to write safe code
>easier
the fact that you just say "easier" without going into any detail is enough to know that you've never written a line of code in your life
>Rust will replace C/C++ the same way C replaced B
B was a personal project used by Thompson and Ritchie while C is in every embedded system on the planet. Not a just comparison in the slightest.

>>105619098
you don't even have namespaces you retarded fucking piece of shit
you have to append fucking backslashes to every line of your absolutely lukewarm macro implementation
until these incredibly basic things are addressed nobody is ever going to start a new, serious C project
you claim memory safety is easy yet new vulns are found basically everyday in well-established projects
just shut the fuck you oaf
I would not be so angry if people like you did not confuse the fucking shit out of newcoders that come here for advice (a very bad idea tbqh). like newcoders will read this shit, think you are correct based on the way you talk, and end up wasting a year of their life on retarded shit.

>>105619098
>if you take even the smallest measures to write safe code
If if if... Rust's idea is to remove that if. There's some value to be seen in that approach, even if you're not a fan of the language.

>>105606490
> type safety
> Go
lmao half the standard library resorts to using reflection.

>>105608214
coroutines in C++ were a mistake. there's like 5 people in the entire world who really understand them, and committee's stance is "don't worry about it, someone smarter than you will give you a library to deal with them".
but even then they are a nightmare to use, because of how easy it is to end up with dangling references, even if you follow best practices (RAII, exception safety, etc).
https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#cp51-do-not-use-capturing-lambdas-that-are-coroutines
it seems like coroutines are fundamentally incompatible with the way we used to ensure basic memory safety in C++. I don't know how Rust handles them, but I'd imagine coros are a horrible idea in any language without a gc.

>>105619442
C++ was a mistake to begin with.

>>105619193
reflection doesn't contradict type safety
it's just dynamic instead of static

>87 reply from one seething ESL cnile
kek

>>105619442
Rust coroutines are actually used in production

>>105606785
How many months HRT?

>>105614353
Rustroons dont live in reality, dont even try to use reason with them

>>105619735
Reason what you dumb nigger? Where is the supposed newly created array? Are you unable to understand English?

>>105619769
You will never be a woman.

>>105619778
You will never be a programmer. Fuck off back to r/unixporn and LARP there. NGMI.

>>105619786
Long way down

>>105605258 (OP)
It already is dying, user numbres are winding down, all the articles written about it today are negative on it... there's no real future for Rust outside of select few places

>>105612417
>imagine getting filtered by deps
>yes its a chore
>but once you get your environment down, you just dont think about it
>and to be honest
>wtf do you even need to be doing to even encounter that as a problem?
and then the time comes where you spend more time addressing CVEs from your 1000 deps, rather than writing code

>>105619833
>It already is dying, user numbres are winding down
2 more weeks

>>105619442
>I don't know how Rust handles them
Futures returned by coroutines are marked whenever they borrow anything and whenever they can be passed around to different threads, depending on how they capture the data and what kind of data do they keep between awaits. Depending on kind of runtime you choose, your tasks might be limited to 'static and/or Send/Sync traits. Eg a single-threaded runtime knows it won't have to pass futures across thread boundaries.
All of this is checked by the compiler. It does remove some obvious foot guns making it harder to make mistake, but async without GC will never be easy either way.

>>105605258 (OP)
In 15-20 years it will be more hated than C++ and corporations would have successfully embedded it in everything just like C++ is now.

All you have to do is track the frequency of adoption for crucial software. If everything you need being written in Rust? Then the shift is imminent. If not, the situation is still fluid.

>>105621438
Did the release of Java followed by imminent rewrite of all the COBOL?
Did the release of Go followed by imminent rewrite of all the NodeJS?
Same thing with Rust and C++.

>>105621460
There is clearly a event horizon that needs to be reached first. That is my point.

>>105621265
Adding to what this anon said. The problem with the C++ example is that an async lambda returns the context of it's state machine which is independent of the lambda (and therefore it's captures) even though it may be dependent on it.
This is just shit. Imagibe if declaring a lambda returned and std::pair of lambda captures and an anonymous callable and you were responsible for ensuring this context exists when the callable exists. It's obviously error-prone, that's why it doesn't do it and the lambda is a callable with the required state bundled together.
Rust also has an async lambda return a future on call, but rather than using a real defined type like std::future in C++ it returns an anonymous object that bundles captures + intermediates in the suspended lambda + data where to resume execution together into one thing that implements Future trait

>>105619098
>marginally, and the difference is insignificant if you take even the smallest measures to write safe code
The funny thing is that saying things like this is why C and C++ programmers keep getting fired. C/C++ people are constantly saying anyone who makes these kinds of mistakes in C/C++ are idiots who shouldn't be coding. Of course companies will fire those people because who wants to have idiots who shouldn't be coding working on their projects?

>>105622247
>https://devblogs.microsoft.com/oldnewthing/20211103-00/?p=105870
there are ways around it, but it's so ridiculous and error-prone that I don't think coroutines should be introduced to the standard in that form (or at all).
I used to work on a small C++ async server which used coros, and it was horrible. you barely can concentrate on business logic, because you constantly need to consider life-times. in this aspect, it felt like going back to programming in C. generally, async programming in C++ is shit imo. I still need to give fibers a fair shake, but I don't keep my hopes up.

Just 2 more weeks

>>105614258
> this is the competency of the average C nile

>>105614300
So it's not creating a new array. Glad we can all agree.

>>105605692
>the issue is rightoids completely give up cultural power willingly so trannies come in and co opt everything.

>If right wingers could stop being retards and start participating in advancing society instead of being brainrotted by conservativism we could have nice things.

or they should just become liberals and join liberal trannies in the fight against the true enemy: leftists

>>105605258 (OP)
Someone will come up with something better, without the mental-illness syntax and faster compilation times and then it will go poof.

>>105624846
Actually believeable

>>105624846
>>105624898
That something is called Go 2.0