[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1733856080779.png (45 KB, 275x312)
45 KB
45 KB PNG
Every single day, more code gets written in C than in Rust.
Every second that passes, Rust troons get further away from their goal.
Just how they will never manage to become women, they will never manage to make Rust useful.

When Rust for Linux started, the kernel had 35 million lines written in C.
Today, the kernel has 42 million lines in C.
>>
Every single day, more code gets written in JS than in C.
Every second that passes, cniles get further away from their goal.
Just how they will never manage to avoid UB, they will never manage to make C useful.
>>
i got filtered by rust, i don't think its going to be a mainstream language if its user base has to be smart.
Its like the phone revolution, it surpassed the use of computers in a matter of years just because its so easy to use.
>>
Rent free.
>>
>>107228548
To be fair, you also have be quite smart to properly use modern C++ as well, and that's the niche Rust targets.
>>
File: 1756523796777388.gif (1.37 MB, 500x300)
1.37 MB
1.37 MB GIF
That's just kicking a man while he's down.
'They' just tried to push that rust-written core utils package to ubuntu and deb, and had shit like chmod, date, and du not passing tests.
So rust devs might not be able to pass, and they certainly shouldn't date, but that doesn't mean they're losing!
>>107228598
See, it has use cases for the !quite-smart
>>
>>107228548
That's why i love rust, one of the rare programming language where I'll never have to deal with jeets.

Also "muh tranny" is a Jewish psyop, 99.9% of rust users are straight white men.
>>
File: 1753592185369160.png (140 KB, 1349x913)
140 KB
140 KB PNG
>>107228827
>That's why i love rust, one of the rare programming language where I'll never have to deal with jeets.
https://rustindia.github.io/
>>
>>107228426
shalom shabbat
>>
>>107228896
are their "PoC communities" near you in india?
not even the person who made this site is a jeet. lmao
>>
>>107228949
>not even the person who made this site is a jeet.
kek rustrannies are sissy sluts for pajeet micropenis
>>
>>107229010
bot fail
>>
>>107228896
>1 star on GitHub
It's so over, pajeetsisters.
>>
>>107228827
You've already been btfo on rust being the designated shitting language, so here's their tranny ratio in top contributors:
https://rustroons.netlify.app/
>>
so now we know what the updated anti-Rust hasbara guidelines:
>don't try to get into anything technical
>go back to only talking about "trannies"
>feel free to make up alternative facts as you go
>>
File: chinkface.jpg (43 KB, 787x787)
43 KB
43 KB JPG
>>107228426
Daily reminder that the UNIX perfection language created by Dennis Ritchie and blessed by Kerninghan himself can't even print without introducing a vulnerability. /g/eets don't know this because they don't give a shit about man pages, but every time you write code like
scanf("%s", buffer);
printf(buffer);

You allow the end user to write at random memory locations. They can even write new assembly instructions to execute. Neat!
Also - friendly reminder that most binary exploitation techniques target flaws introduced by the language itself, not logical errors. All allowed by the language that prefers to crash at runtime instead of catching trivial shit at compile time. Friendly reminder that Python was modeled after C.
>>
>>107228716
> and du not passing tests
All, or most, like 99.999% of rust code was translated from C with a LLM and/or c2rust. Rust proponents don’t even know what those utilities do.
>>
>>107229490
No, it was not. The coreutils license doesn't allow this. Anyways, do cniles even know their own language >>107229449?
>>
>>107229449
It’s fine for test code, or if you put a guard page past the buffer. Oh, it’s a hundred times faster, too.
You clearly don’t know how computers work, and probably don’t know what I’m talking about.
Go back to your comfort zone: Logo or Scratch
>>
>>107229532
>put a guard page
Behold, a cnile who randomly heard "buffer overflow" and tries to sound smart, while missing the actual vulnerability entirely.
Or a disingenuous mossad agent. Please do know that God has a solution for all you glowie niggers
>>
>>107229532
Also
>runtime function call
>faster than doing it once at compile time and storing the result
Brightest programmer in the Bharat
>>
>>107229449
>warning!! don't use printf like this!!!
Thanks for the heads up Rajeesh
>>
File: mason-mason-67.png (116 KB, 498x497)
116 KB
116 KB PNG
>>107229820
>completely misinterprets the main point to divert attention from it
>ad hominem no u about jeets
At this point I'm convinced I'm talking with actual glowies here
>>
>>107228426
that's a retarded amount of code.
>>
>>107228426
>Every single day, more code gets written in C than in Rust.
Proving the point that C++ never took over from C and somehow you expect Rust to take over from C overnight. Learning Rust means learning how the borrow checker works which is not easy and requires a whole new way of thinking about code. Rust hasnt reached that threshhold yet where programming with the borrow checker in mind is mainstream, but eventually it will unless someone invents some whole new way of programming
>>
>>107230692
6.18-rc6 has ~31M lines of actual code (not comments or blanks), ~27M of which is C code (including ~8M in headers).
of that ~27M, ~20M lives in the "drivers" sub-directory.
not that it needed stating, but op is yet another retarded nocoding /g/eet.
>>
>>107231211
that's a retarded amount of code.
>>
>>107231496
not really. between arch, fs, net, ...etc, it splits out.
and there is still device/driver stuff outside of the top "drivers" sub-directory.
and there is also non-kernel code in-tree like the ~1M lines of code in the "tools" sub-directory ("perf" et al).
>>
>>107228827
only people ive seen shilling it without hiding behind an anime profile pic are chinks
>>
>>107228896
>no resources on the website
>dead github since 2023
ngmi
>>
File: image-94.png (46 KB, 960x1011)
46 KB
46 KB PNG
>>107228426
>Every single day, more code gets written in C than in Rust.
I only need HolyC
>>
>>107229449
>what is fgets()
>>
>>107228548
rust isn't hard though, it's pretty similar to typescript or some shit. If you literally ever need to use any of the retarded <`ctx> lifetime bullshit you're probably doing it wrong.
>>
>>107231211
Now tell us how much rust code is actually relevant thats in the kernel.

Because that is the point that got made. You aren't arguing against it.
>>
>>107232488
Rust is an ugly as hell language that only survives on government money (and doesnt even do that well).

99% of people writing Rust either:
>let an auto converter or AI convert from C to Rust and then keep looking through that vomited code to fix it
or
>have C code open one one side to rewrite it into Rust in anther
Nobody does that shit voluntarily. Imagine living like this! Imagine how incredibly pathetic this existent must be.
Even a javascript jeet code monkey has more fun, freedom and creativity in his job.
And then they use terms like cniles to describe the people who write the code that they copy and look at the whole day to rewrite.
You are living downstream of them! If you hate what you do, then why do you do it?
>>
>>107229449
kek good troll
>>
File: 1626976570790.jpg (69 KB, 695x811)
69 KB
69 KB JPG
None of you retards got it
>>107229532
>>107229820
>>107232041
>>107232960
There's no buffer to overflow here. Google "format string exploits". This class of bugs is exclusive to C because it does
- string formatting at runtime
- variadic functions at runtime
No wonder you got filtered by Rust >>107232954, you don't even know how C works
>>
>>107228426
gemerald.
saved
>>
File: 1763369241748.png (494 KB, 615x615)
494 KB
494 KB PNG
>gemerald.
>saved
>>
File: 1741071959768974.png (772 KB, 1118x1120)
772 KB
772 KB PNG
I don't know if these threads are made by jeets, glowies, soi jack kids or LLMs. Please just give me the old 4chan back.
>>
Reminder that the four prestige Rust projects are:
>rav1d, the rewrite of the dav1d AV1 encoder
Got auto-converted into unsafe{} rust by c2rust, after c2rust was part of another DARPA funding round.
Then troons took the generated slop code and try to get rid of somce unsafes{}, and failing, while trying for years, their encoder is 5% slower than the original, even thought that it is literally a convert.
>apple drivers of that vtuber troon
Never made it insto stable, is ridiculously buggy and the troon quit. It is dead.
>sudo-rs
Is insecure by design. You take something that is faulty and a bad-practice, and rewrite it into Rust, so that you can do insecure bullshit in a different language.
They rewrote this and at no point they thought: "You know what, this thing seems to be kinda bad"
They never had enough autonomous thinking that while literally copying sudo, rethinking if the concept itself is even good.
Meanwhile Poettering delivered run0, an actual better alternative, in about one month and it is stable. Written in C.
>uutils
They literally have the most extensive test suite in existence, the one of the GNU coreutils to their disposal. The only thing they have to do is to run the GNU tests and implement what the tests say is faulty.
And they somehow fail even that. Also of course their development is government paid.

All Rust projects fail because of two very simple reasons:
>the language is not fun
>the ones writing it are government paid monkeys who don't care
>>
>>107228426
Almost as if they know that they can't reach their goals by themselves, so all their focus is on trying to scam others into rewriting things.
>>
>>107233219
>Please just give me the old 4chan back.
>the NIGGERFAGGOTREDDITFROG says
Die.
>>
i see more compilers being written in it than the language itself being used for other things. which is kinda funny but i think an actually semi-reasonable use case.
Even though Ocaml 5 is probably still a better choice
>>
>>107231790
does this mean Rust kills jeets?
>>
>>107228426
a couple of years and rust will be forgotten and a new language shilled as the C replacement will surface
>>
>>107229449
>user can rm -rf /
>"lmao shit os it allows the user to kys itself"
ansolute state of rustroons
>>
>>107229325
I said users, not contributors.

Troons are attention whore and they will autisticaly waste hours of their life for the smallest crumbs of it.
Straight white men only care about getting things done, they are much less likely to be contributors.

Instead of looking at contributors look at software build with it.
>>
I wonder if Rust was such a nothingburger, why /g/ keeps seething about it everyday.
Hmm
>>
File: distrust-the-science.png (26 KB, 353x315)
26 KB
26 KB PNG
>>107234202
>seething about it == tranis posting bait and c-ultists showing why its a bad idea to do so.
>>
File: 1737685471419.png (44 KB, 360x292)
44 KB
44 KB PNG
>>107234202
>>
>>107229520
His statement, that all or most, like 99.999% of rust code is translated with tools, is correct.
c2rust is responsible for the vast majority of rust code out there.
That's why all rust projects are littered with unsafe{}, even in cases where it isn't needed.
That's why the rust shills pretend as if their project is memorysafe, and then are surprised when someone looks at the code and discovers that almost all of it is nested inside unsafe{}.

rav1d was shilled so incredibly hard here by people who don't use it and never looked at the code.
Yet you are projecting this onto your "enemies" and claim that "cniles" don't know c code, while you routinely demonstrate that you don't know a single Rust project.

And if you think that the people who write the C code that you copy to rewrite, are somehow incompetent.... then why do you copy their stuff? Why not make your own?
Clearly they are capable of creating things.
>>
>>107229449
C does it the worst possible way. It uses format strings that have to be parsed at run-time, but also has no type safety, and memory vulnerabilities, and you can't add your own formats. C stole that idea from BCPL, which is a language with no types or memory safety. Lisp format strings are completely type safe and memory safe, with conditions (exceptions) if there is an error. Lisp lets you define your own PRINT-OBJECT methods to control how custom objects get printed. Lisp formats can also be compiled into function calls using a built-in compiler macro, which makes them a lot faster than C because there's no string parsing at runtime.
>>
File: cve-rs.gif (273 KB, 1200x600)
273 KB
273 KB GIF
>>107234832
>muh safety
ok, soapbox is yours, then
>picrel
...
>>
>>107228426
I love how these retards still haven't responded to the google blogpost.
you lost.
>>
>>107234117
I don't understand why I'd ever use Rust if I already know Haskell and don't write latency sensitive systems code. Haskell can already do linear types and skip GC if you need peak performance so I don't get Rust's purpose.
>>
File: modern-sepples.jpg (149 KB, 800x533)
149 KB
149 KB JPG
>>107234858
post link
99% of prob im gonna call it preposterous
an attempt at corrupting the youth
and call you a faggot
>>
>>107228896
not that I care for this behavior, but all the jeets I knew were big C tards and hold the same moronic opinon of most /g/ posters. Made me realize that maybe /g/ is full of browns, unironically.

real "whiteness" is realizing when something better exists and actually using it.
>>
>>107229449
I am reminded the GTA V loading debacle caused by using *scanf family functions in a loop to parse assets too. It really is a shit lang with a shit stdlib.
>>
>>107234869
https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html
enjoy.
>>
>>107234892
>https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html
baste cya in 30 mins or so
>>
>>107234892
make it 5 secs actually
sample selection bias: interns + big, flaccid, overweight, impotent corpo
>>
>>107234929
>no response
without fail. Rust keeps winning it seems.
>>
>>107234874
I know only 1 jeet which was in my classes and he loved Java, I mean he isn't even a jeet but from Nepal but it's almost the same
>>
File: redpill-tech.png (517 KB, 644x1148)
517 KB
517 KB PNG
>>107234892
>>107234929
forgot pigrel
r&d is expensive when you have 5 managers for each guy thats actually in the trenches
>>
File: ngl-based.png (446 KB, 1000x837)
446 KB
446 KB PNG
>>107234934
>selection bias is no answer
go back to 10th grade maths
stats and such
>>
>>107234949
>I got completely buckbroken by objective real world data and can only cope
ya, I know. Rust won.
>>
File: rust-jobs-shrug.png (70 KB, 523x720)
70 KB
70 KB PNG
>>107234960
yeah
>rust winning
suuure
>>
>>107234965
>still can't reply to the fact the Rust code has less bugs and is easier to read & review
keep it up kiddo. Rust won.
>>
>>107234965
You need about 100 C++ programmers to do the same work as 1 Rust programmer.
>>
File: modern-languages.png (28 KB, 441x349)
28 KB
28 KB PNG
>>107234975
yeah but you have another degree of abstraction which isnt something you want in many cases.
most cases, actually

guess what language this one is
>>
>>107228426
>more code gets written in C than in Rust.
True, but only because coding in C is crazy inefficient. You need to write so much code that it's not even fair to compare to other languages.
>>
>>107234997
its all a matter fo control
and reusing the code but hopefully youre not alluding to that...
thats cs 101 shit
literally the concept of a function/library
>>
>>107234997
there is also the practical reality that a lot of code out in the world is legacy boomer trash, possibly using some NIH garbage C toolchain that no one can really move off of without introducing dangerous bugs and unexpected behavior. hell, a lot of corpo cucks seethed when git started writing new functionality in rust because their boomerware trash UNIX systems (think like HP-UX, etc) don't have working Rust toolchains (and LLVM in many cases).

the world is a disgusting mess, most retards don't even realize a lot of real world COBOL is still written for similar reasons.
>>
File: rust winner.jpg (893 KB, 1024x1024)
893 KB
893 KB JPG
I tried programming in rust and it honestly felt like I'm being watched and constantly reminded to do basic things like wash my hands or stop rubbing shit into my face even though I wasn't doing it. Really uncanny how this shitlang can be liked by anyone but total subhumans who need a smartwatch to remind them to breathe through their nose.
>>
>>107235026
>t. never used static analyzer
>>
>>107235015
>the world is a disgusting mess, most retards don't even realize a lot of real world COBOL is still written for similar reasons.
COBOL is a better language than C and C++.
>>
>>107235045
I use my brain already.
>>
>>107234202
>why /g/ keeps seething about it everyday.
this is not true. there weren't any such posts during shabbat.
>>
File: oppenheimer-gun.jpg (183 KB, 980x653)
183 KB
183 KB JPG
>>107235045
>static analyzer is gonna prevent data dependent errors
>aka 99,9999% of the code in the wild
>>
>>107235026
idgi, is that your hand or something? because your retarded comment tracks with that pic very well.
usually the most delusional retards are the ones that need babying the most.
>>
>>107235063
>>107235075
>mention static analysis
>seethe in response
Kek. Unemployment general
>>
>>107235088
>usually the most delusional retards are the ones that need babying the most
That's why I refuse to use a shitlang for delusional retards.
>>
File: viper.png (447 KB, 750x750)
447 KB
447 KB PNG
>>107235094
>implying being a wagie is a distinction in any way
arent you supposed to look busy at this hour of the day?
>>
>>107235096
so you're admitting you need more babying the average dev??? do you know how to read, retard? Ya you should be using Rust, because you probably write some of the most liquid diarrhea shitcode imaginable.
>>
>>107234994
>>107235007
That's terrible code. Real languages have multidimensional arrays for this exact reason. FORTRAN had them since the 50s.
>>
>>107234858
i told you since friday that it make take until monday (>>107204634).
now that we have shabbat and sunday out of the way, you're seeing the jeet hasbara and (((friends))) in full force again.
>>
>>107235109
>That's terrible code
it's OpenCL, so ya, of course it's woefully inadequate for what it's designed for.
>>
>>107234729
>constant blabbering about rav1d
>muh c2rust
This is the only rust project you know of, right? Because you've never actually used it
>>
File: todd-howard.jpg (70 KB, 512x681)
70 KB
70 KB JPG
>>107235109
yeah but thats not why you use the other languages
theres a ton of implicit things going on behind the scenes some of which i dont even fukken understand

but to give you an idea:
i tried re-writing one of the intrinsic based float multiplications into an idiomatic manner
it increased the runtime by 25%
one sole multiplication

c gives you the most control without actually needing to do asm
and you have extended c which is how the compiler reacts to the code, in the outupt, and how that, in turn, interacts with the finer elements of the processor
like instruction level parallelism, and out of order operations
>>
>>107234929
lmao >>107204806.
originality is not something you can "accuse" /g/eets of.
>>
File: zuck-stalker.jpg (119 KB, 950x970)
119 KB
119 KB JPG
>>107235112
>>107235137
ah shit you posted the other thing
>>107235125
no, its cuda
but point still stands, you want a granular control over whats the goings ons and such
like when you want to coalesce reads although im not sure if cuda doesnt do that behind the scenes
>>
>>107235112
starting to wonder if there is some schizo truth to it, but I think it isn't for some nefarious reason to convince people to use C over Rust, but to just shit this place up in general. they tune the bots to fit the board and low IQ word diarrhea defending and promoting C is apparently on-topic.
>>
File: 1744479975011024.jpg (41 KB, 736x711)
41 KB
41 KB JPG
>>107235026
This is the actual reason jeets hate Rust. It reminds them of their incompetence. If you can't pass the borrow checker and don't even understand why it screams at your spaghetti then you shouldn't be touching any pointers kiddo
>>
File: pepe-newspepe.jpg (355 KB, 1391x1405)
355 KB
355 KB JPG
>>107235141
or maybe its just the logical responses to your cope?
>nuh its bobular
no, it has like 1% of sepples jobs
>bud bic companies use it therefore you should too
uh, no, they have a different usecase
they have to wrangle tards. plus theyre impotent so they use all the help they can get
>>
>>107234965
lmao again >>107204806.
originality is definitely something you can't "accuse" /g/eets of.
>>
>>107235155
Borrow checker doesn't check pointers though?
Do you even know anything about Rust other than that you're qualified to be its user?
>>
>>107235165
His point is you can't even write correct code in the best possible cases and you can't be trusted to handle memory correctly at all, and he's absolutely correct.
>>
>>107235165
It checks references, which are a pointer type in Rust. You really never even used the language. But that wasn't even the point, see >>107235197
>>107235149
Friendly reminder the "fukken" "lamao" guy doesn't actually works in computer science, he paints walls. This is why he insisted malloc is a syscall, that templates are less efficient than void*, he's actually a skid without assembly knowledge and spams rust threads every single day for the past 3 years
>>
File: laughing_caprio_jesus.png (266 KB, 400x400)
266 KB
266 KB PNG
>>107235197
>His point is you can't even write correct code in the best possible cases and you can't be trusted to handle memory correctly at all, and he's absolutely correct.
homofag
>>
I've moved to using the lisps and everyone I've interacted with is an old straight white male. Sure in 20 years no one will be left but if you start using lisp now you will be the future wizard some young buck seeks the wisdom of.
>>
>>107235155
>If you can't pass the borrow checker and don't even understand why it screams
It screams because you tried to implement any nontrivial data structure that involves multiple mutable references to some data.
>>
File: w11-devs.png (413 KB, 546x502)
413 KB
413 KB PNG
>>107235205
no fucking way
i have fukken followers my absolute sides

nah youre just jealous i went from calling malloc a syscall to writing opencl and intrinsics in 3 years
>>
>>107235210
Why can't you actually address any actual points? What the fuck is your problem? Is the other anon right? Are you some Israeli spam bot or just incredibly low IQ?
>>
>>107235223
i did address your points
why arent you addressing the counter?
>>107235162
yeah, thats me
>>
>>107235218
This is a strawman, most people don't reimplement linked lists every single day. Unless they're cniles because their stdlib doesn't support it
>>107235222
At normal universities you go from writing C to assembly and cuda in a year
>>
>>107235238
yeah, im self taugh
also thats another layer to the thing
i took me 3 years
its not like it went fast
>>
>>107235241
>im self taugh
We know
>>
>>107235232
No, you literally didn't. You're asserting you're correct despite a known practical model telling you otherwise and cannot give actual feedback why it's wrong, because you don't understand either.
>>
File: zero-cost.png (281 KB, 900x966)
281 KB
281 KB PNG
>>107235223
NTA but I'm not seeing any "actual points" made by Rust users ITT, either. Rust's borrow checker -ACK's when faced with correct code. In fact, the overwhelming majority of correct solutions to any given problem are impossible to express in Rust.
>>
>>107235238
>This is a strawman
Then how come you immediately went on to concede my point with the clownish excuse that most people "don't need" to implement nontrivial data structures "every day"?
>>
>>107235255
The fact you can't model the correctness is part of why you're wrong. You're literally low IQ. The borrow checker isn't magic, but it's literally the most state of the art static analysis that provably works at Google scale.
>>
File: C-hurch.jpg (91 KB, 806x527)
91 KB
91 KB JPG
>>107235250
why its wrong?
bc it gets in the way
simple as
yeas c is unsafe. yeah you need competent people to do a good job.
yeah.
big deal. c is awesome bc it gets out of the way.
if youre good and your mind bends in the direction of c you wont make mistakes
if i, a permanently under the influence self taught can have 20klocs with zero mem errors, anybody can.
you got 0 excuses for being sloppy because its not even a matter of iq
its just a matter of method and thoroughness
>>
>>107235162
so true.
i'm looking into becoming a code cabbie myself. what do you recommend? hyundai or maruti...i mean JAVA or C#?
>>
>>107235272
Clearly, I can model the correctness because I have correctly determined that the program is correct. It's just not expressible in Rust because Rust is trash.
>>
>>107235280
Compile your code with -fsanitize=address and run it.
>>
>>107235291
Ok, now prove it.
>>
File: clown-b.jpg (75 KB, 680x480)
75 KB
75 KB JPG
>>107235287
i have no idea
i went through a semi formal education in programming when i was 30
employement was never an option for me

id say go versatile
make hr wet thei aint technicals anyways
make sure to list every framework idk thats what id do
>>
>>107235300
>now prove it.
I don't need to. It's well-known and noncontroversial that Rust will reject most correct programs because it's overly conservative on one hand and extremely inexpressive on the other.
>>
>>107235265
>cniles to this day cannot grasp the concept of writing a generic data structure once and reusing it as a library
Also linked lists are trivial. They're a building block for other data structures. Read SICP
>>
File: buffers-g.png (180 KB, 865x740)
180 KB
180 KB PNG
>>107235294
>babby shit
rather i do valgring
afaik -fsanitize=address does a static analysis
valgrind does a dynamis test dpeending of your data, you use it for algorythmic errors too
or tahts what i do, you do what you ploease
>>
>>107235314
>>it's correct because I say so even though rust says it's wrong
>ok prove it
>>Um I don't have to prove anything
you're a fucking schizo retard, huh? I wish we could round up schizos and stick them in asylums so they'd stop shitting up the Internet with their magical thinking and deranged arguments.
>>
>>107235314
The only thing I get from cniles here is that all they do is write linked lists and self referential structs. This is all they do all day long. For people who spout performance you sure do love your cache misses
>>107235328
>doesn't know what asan is
The power of /g/
>>
File: C-pookie-posix.jpg (45 KB, 730x411)
45 KB
45 KB JPG
>>107235335
i even used it
but then valgrind, and i got hooked, and now idc, i dont even remember a time before, man
>>
>>107235317
This. Pretty much anyone who can write C++ and Rust can make them in Rust. Rust just points out some edge cases you didn't think about while you're writing them desu. Real eye opening. Either way, the equivalent rust doubly-linked list looks basically the same as C and C++ just with some scary looking mem::* functions.
>>
>>107235317
>linked lists are trivial
I agree. In addition to nontrivial data structures, Rust is also antagonistic to trivial ones.
>>
>>107235350
Rust is keeping you honest. The fact you can't understand that is why you shouldn't be allowed to write C or C++ code.
>>
>>107235350
rust is just hostile design
kinda like fighting hobos
but as programmers

their problem is that EVERYTHING is behind hostile design
>>
>>107235345
Asan serves the same purpose as valgrind. Also how retarded do you have to be to prefer dynamic analysis over compile time errors. Cniles bitch about passing their borrow checker then spend their whole day in gdb and asan/valgrind
>>
>>107235333
See >>107235314. Wipe the foam off your mouth, take your meds and then reflect on the obvious truth of what I wrote: there is nothing wrong whatsoever with having two mutable references to a piece of data. Rust simply doesn't allow you to express the intended usage pattern let alone verify that it's adhered to.
>>
>>107235350
>linked lists are trivial
I agree. In addition to nontrivial data structures, Rust is also antagonistic towards trivial ones.

>>107235360
Rust is keeping you mentally ill.
>>
>>107235374
There is everything wrong with two mutable references to a piece of data that is not synchronized in some fashion.
>>
File: kottest-kot.jpg (54 KB, 1125x1125)
54 KB
54 KB JPG
>>107235368
lole, ure stupid

heres an example:
you open a file
the first few bytes define the size
but youre given the wrong size of bytes so you buffer overflow your allocation
boom
static analysis is not gonna catch it

why crabs are retarded, apart from the fact theyre one step removed from mollusks?
cephalopods are smart
why cant you be more like cephalopods?
>>
>>107235360
Ok but I have better things to do than dance around with &mut [MaybeUninit<T>] all day just because retards like you cause segfaults and basic logic bugs for a living.
>>
>>107235385
>here is everything wrong with two mutable references
Thanks for overtly displaying your psychotic mental illness. This is where your cult diverges from programming. There's no discussion to be had with a mongrel who writes such a thing unironically.
>>
>>107228426
https://youtu.be/HX0GH-YJbGw?t=184
>>
why is rust syntax so niggerlicious
>>
>>107228535
Kek they’re ignoring this because they have no argument for it
>>
>>107234994
C with namespaces?
C++?
>>
>>107229449
>All allowed by the language that prefers to crash at runtime instead of catching trivial shit at compile time.
This is a good thing when done well though. BEAM is the best language runtime period for this very reason.
>>
This is probably the most unintelligent thread on /g/ right now. Sasuga cniles.
>>
>>107235500
C doesn't have a garbage collector and its not based on the actor model. Apples and oranges
>>
>>107235500
>crash loop, le good!
>shitty untyped runtime slop like BEAM bytecode, le good!
no.
>>
File: rust-breaking-linux.png (199 KB, 802x842)
199 KB
199 KB PNG
>>107235507
>>
>>107235389
>static analysis is not gonna catch it
But it will catch an unhandled exception through its type system (the Result type). Rust would prevent this.
>>
>>107235515
Well thought-out reply.
>>
File: rust-security.jpg (181 KB, 1793x1179)
181 KB
181 KB JPG
Soowuuuhhhh... is there any particular reason why humanity has to stick to a fundamentally braindamaged computing model, keep stacking layers upon layers of buggy and inherently vulnerable software on top of it and then desperately cope with the infinite security holes by peddling disgustingly unproductive and unusable programming languages?
>>
>>107235514
>crash loop
>doesn’t understand anything about BEAM other than le static vs dynamic typing
The of a midwit is placing static typing above all other aspects of a language.
>>
File: 1760892451195416.jpg (27 KB, 461x461)
27 KB
27 KB JPG
>>107235515
Read, nigger, read >>107229520
They reimplemented everything from scratch without actually looking at the original code. Does it have bugs? Yes. Are they getting fixed? Yes. Did it take them decades to write like coreutils? Hell no
>>107235539
>Mossad glowies getting dunked on so hard they resort to fake ragebait images
>>
File: laugh-tale.gif (52 KB, 220x273)
52 KB
52 KB GIF
>>107235539
Cool graph you got there. It would be a real shame if it was just a fake graph made by Twitter troll trying to bait people who have no idea what they are talking about.
>>
Why are all Rust users mentally ill? You don't see this unhinged cult-like behavior with any other programming language. Not even Lisp.
>>
>Rust-haters are now "Mossad"
Rust users confirmed Christentroons
>>
>>107235563
>You don't see this unhinged cult-like behavior with any other programming language
Have you looked at this thread? Sane engineers do not talk like this.
>>
>>107235563
>spew retarded ragebait lies about a language you don't even use
>people who use it correct you
>holy moses we're being genocided by cultists, this is le another shoah!!!
>>
>>107228535
>c is trying to replace js
rust trannies are completely buck broken
>>
>>107235563
>Why are all Rust users mentally ill? You don't see this unhinged cult-like behavior with any other programming language. Not even Lisp.
this. there's definitely something wrong with a language whose school of thought distorts the minds of its users to this degree, regardless of any alleged technical merits
>>
File: warning for rust users.jpg (150 KB, 526x526)
150 KB
150 KB JPG
>>107235563
Because they're the reason why warnings like picrel are necessary.
>>
>>107235611
>using Rust to stop memory errors is like using your genitals to stop a chainsaw
Hm. Yes, that makes sense.
>>
>>107235629
I use my brain to stop memory errors and I use my brain to stop my chainsaw, but the way my brain does it a bit too complex for you, to understand.
>>
>>107235589
It's called being tired of jeets. Tired of seeing their lies. Tired of seeing their shit code and shit opinions online. If India was nuked we wouldn't have Rust hate threads in the first place
>>
>>107235539
Uhh, cnile bros? https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html
>>
>>107235589
>there's definitely something wrong with a language whose school of thought distorts the minds of its users to this degree
I've always wondered about the causality here. Does it simply attract people who are mentally ill to begin with, the way niche and deformed ideas tend to do? Or does it actually drive its users insane? Is it a little of both? Someone needs to study this community.
>>
>>107235678
It is designed by mentally ill, for mentally ill. https://rust-lang.org/policies/code-of-conduct/
>>
>>107235697
>Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
Too bad this is an anonymous board and you can't report them to their own community for continually violating the Rust Commandments. :^(
>>
File: 1757465498235732.jpg (71 KB, 912x1024)
71 KB
71 KB JPG
>>107235563
>>107235589
>>107235678
I've always had a bad gut feeling about Rust, and that's all I need to know something's wrong with that language. It's a mixture of its proponents and the language's asinine goal, I think. Feels a lot like the corona mRNA vaccine.
>>
>>107235678
I remember early Rust (before they threw out GC in 2014) and it wasn't bad, I think it got much worse over time
>>
>>107235678
>>107235697
>>107235740
>>107235750
>>107235763
Assblasted so hard their incompetence got exposed they cry about "muh community" instead
>>
>>107235651
I remember this post. It went so hard (((they))) had to remove it
>>
>>107235411
you won't get replies to this, ironically for a reason not related to rust.
a center talking point the jeet hasbara and (((friends))) try to sell to the nocoding tech illiterate masses is that all projects using C out there are relying on decades-old well-established "muh battle-tested" INTERNATIONALLY-STANDARDIZED tech.
turd worlders, jeets in particular, cartoonishly give too much credence to ISO and co, because just like the UN, they think it's real authority, and they think they are a real part of it.
>>
if you ignore Rust trannies they eventually go away like any other BPD sufferer
>>
>>107235821
>if you ignore Rust trannies they eventually go away like any other BPD sufferer
They're obsessed with being "marginalized" and "excluded". There's nothing more satisfying than entering a thread where people are talking about Rust while ignoring the screeching Rust users. It inflicts real emotional harm on them.
>>
File: screenshot.jpg (60 KB, 691x182)
60 KB
60 KB JPG
>>107235815
It's okay, we have systems in place against (((them))). Truth does not fear censorship.
>>
>>107230498
>>completely misinterprets the main point to divert attention from it
yes we get it passing some random user inputted string to printf is... le bad because of formatting. you are not tuff for knowing about this behavior
the only place I interpreted it as a buffer overflow is in your dalit head btw
>>
>>107235976
Heartbleed was caused by white programmers.
>>
File: 1728983402854403.jpg (15 KB, 320x213)
15 KB
15 KB JPG
>>107235998
Explain this to me - why should a printing function allow arbitrary memory writes for the end user in the first place?
>>
File: screenshot.jpg (217 KB, 831x284)
217 KB
217 KB JPG
>>107236014
>>
>>107236034
it's a printing function with formatting
>>
>>107236034
If you don't like it, don't use it, tranny.
>>
File: katze10.jpg (191 KB, 1536x2048)
191 KB
191 KB JPG
>>107235976
The jews fear this post because it united all competent C, C++ and Rust programmers with a common goal
>>
>>107236047
>>107236053
>no arguments
Again - a printing function that allows arbitrary write access TO THE FUCKING END USER. Acceptable only in cnileland
>>
>>107236079
Arguments against what?
>>
>>107236079
It only allows this to the end user if a programmer who uses printf is a drooling mouthbreather, why don't we talk about that part, rakesh?
>>
>>107236079
you're ignoring the f part of printf in your own argument because you're a dumb gorilla ape.
>oo oo aa aa
look at the monkey go
>>
>>107235642
>cniles are jeets!!!
>cniles are jews!!!
>cniles are trannies!!!
your desperate attempt to deflect is pathetic and not persuasive
>>
>>107236045
German
>>
>>107236095
>>107236104
>>107236108
>>107236114
Instant butthurt and discussion derailing. Typical jewish tricks.
>formatting input implies unsafety
>hurr durr the end user should know about the existence of an obscure format specifier that no sane person even remembers
I'll bite. Why does a printing function (i.e - output to stdout) allow ARBITRARY access to memory. Not even overflowing the stdout buffer or something but actual "pass an address into stdin and I'll write whatever you want there habibi"
>>
>>107236157
Just like those two German banks that funded Adolf Hitler.
>>
File: image.jpg (547 KB, 1280x720)
547 KB
547 KB JPG
>>107236177
I don't know why you wrote your code to have a bug like that, doesn't happen in my code.
>>
>>107236181
Yeah. The point is, there was no jeets behind any of the large CVEs we got. It's all just competent programmers making honest mistakes.
>>
>>107236104
>no, you see, everyone who expected printf to work like in any other language is actually a retard. Writing printf(buffer) is retarded, and everyone knows about "%n". This is purely their fault, writing printf(buffer). Because there's no use case to printing a burffer.
>>
ITT: cniles discovery format string vulnerabilities
>>
>>107236213
I expect first printf argument to be a compile time string and not for some mysterious reason taken from the user. But I'm not jewish so I'm not educated in such blatant backdoors, can you shed some light on why your format string is taken from end user if that's a problem to you?
>>
>>107235137
Your whole post is sour grapes and baby duck syndrome.
https://en.wikipedia.org/wiki/The_Fox_and_the_Grapes
>The story concerns a fox that tries to eat grapes from a vine but cannot reach them. Rather than admit defeat, he states they are undesirable. The expression "sour grapes" originated from this fable.[3]
>>
>>107236240
>food analogy
>>
>>107235137
>c gives you the most control without actually needing to do asm
Let's see how you would implement async/resumable functions in C without asm(or RTOS which also uses a lot of asm)
>>
>>107236177
>continuing his careful use of semantics
apply to be part of the idf
>>107236213
if you want to print without formatting then why are you using the print with formatting function
>>
>>107236177
>Why does a printing function (i.e - output to stdout) allow ARBITRARY access to memory.
Who cares? It was designed 40 years ago and it stuck because sometimes it's convenient. If you don't like it, don't use it.
>>
File: 1733170542521.png (2.51 MB, 1439x1443)
2.51 MB
2.51 MB PNG
I thought that Rust is actually good.
But then i checked out uutils and everything i saw was rookie mistakes and obvious vibe coded converts.
They can't even get something simple like printing a date correct. Even when you hold their hands and give them an extensive test script that tells them exactly what is missing or faulty.
And everything is ugly and horrible to work with.
>>
>>107236299
This is not an issue in Rust, even though it provides formatted printing
>>107236327
Yes, I use Rust instead
>nooooOOO NOT LIKE THAT!!!
>>
>>107236346
cool, then create something in Rust.
Somehow that's the one thing you all always fail at: Building stuff.

Make it better.
It's all up to you.
Currently Rust is some fringe language that barely anyone uses, and the ones who use it are vibe coding.
>>
>>107236346
>I use Rust
Ok. So why are you obsessively screeching about C functions you don't use? Is it because you're mentally ill? Yes, it is.
>>
>>107236367
>>107236376
The jews truly are masters at diverting the attention of the common folk
>why are you screeching about C
Who makes these anti-Rust threads in the first place nigger?
>>
File: oop-spirituality.jpg (52 KB, 625x1000)
52 KB
52 KB JPG
>>107235840
>They're obsessed with being "marginalized" and "excluded". There's nothing more satisfying than entering a thread where people are talking about Rust while ignoring the screeching Rust users. It inflicts real emotional harm on them.
wise words that posters ITT could benefit from contemplating
>>
File: 1761580996015.jpg (28 KB, 500x460)
28 KB
28 KB JPG
>>107236384
>>
shabbat shalom everyone. we missed you. especially the tech illiterate nocoder zoggie e-celeb.
>>
>>107236384
>Who makes these anti-Rust threads in the first place nigger?
Probably members of your cult, because it's the only way your irrelevant language can get any attention outside of a corporate and alphabet soup agency context.
>>
the anti-C schizo in this thread seems to have a lot of free time to shitpost. why don’t you get a job? is it that there are no rust jobs?
>>
>>107235563
The only cult-like behavior in this thread is coming from Ctrannies. Rust programmers are sane and normal people, who are responding to absolutely insane lies from Ctrannies. Ctrannies act like they're possessed by demons and Rust is an exorcist.
>>
rust users in this thread ARE building things, right now as we speak. they're just waiting for compile to finish. then once that's done, surely they can debloat the massive output binary by importing a debloating rust crate. Rust Yes!
>>
>nOOO DON'T TELL THE GOYIM ABOUT VULNERABILITIES BAKED INTO THE C STANDARD BY ANSI AND ISO!!! That's antisemitic!!!
>Lets talk about hypothetical rustc backdoors instead
>noo noo don't actually decompile anything, that's too hard for goyim:-)
Now watch this thread get instantly derailed by glowies because people did notice
>>107236400
>>107236413
>>107236414
>>107236423
>>
>>107236415
>The Cniles are whispering to me through the walls
>they are violating the Rust TOS
>oh god make them stop aaaahhhh
>i hate scanf i hate scanf i hate scanf...
Ok...
>>
>>107236432
take your meds, you’re having an episode
>>
>>107236415
Kek this.
>>
>>107236432
>incompetent glowgroid trying to simulate /pol/speak and make Rust look cool
Maybe if you write 150 more posts like this it will catch on.
>>
>>107236459
>/pol/speak
How about you go back?
>>
>>107236465
Very good. Now do "Christ is King".
>>
>>107236474
I'm not christian and neither you are.
When was the last time you went to a church and confesses your sins?
>>
>>107236459
It's so transparent what those subhumans try.

You literally shill for a DARPA project that is predominantly run by transsexuals, because those are the people those government projects hire... and do it by emulating /pol/ speak out of some weird reason...
They are so out of touch, it is unreal.
>>
>>107236500
You're not allowed to go that far, huh. Ok. What else is in your database? :^)
>>
low IQ thread.
Rust won regardless.

keep coping shitters.
https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html
>>
>googleblog
lol
>>
>>107236288
#include <stdio.h>

enum tranny_acking_status {
INIT,
IN_PROGRESS,
NOT_YET,
ALMOST,
YOU_MAY_ACK_NOW,
CLEANUP
};

struct tranny_acking_context {
enum tranny_acking_status where;
int times_called;
};

int eventually_ack_all_trannies(struct tranny_acking_context* const ctx) {
static void *jump[] = {
[INIT] = &&init,
[IN_PROGRESS] = &&in_progress,
[NOT_YET] = &&not_yet,
[ALMOST] = &&almost,
[YOU_MAY_ACK_NOW] = &&you_may_ack_now,
[CLEANUP] = &&cleanup
};
goto *jump[ctx->where];

init:
ctx->where = IN_PROGRESS;
ctx->times_called = 1;
return 0;
in_progress:
puts("Starting to kill trannies...");
ctx->where = NOT_YET;
ctx->times_called++;
return 0;
not_yet:
puts("No, Timmy, trannies are not yet dead...");
ctx->where = ALMOST;
ctx->times_called++;
return 0;
almost:
puts("Yes, Timmy, we're almost done...");
ctx->where = YOU_MAY_ACK_NOW;
ctx->times_called++;
return 0;
you_may_ack_now:
puts("Okay tranny, you have an option to kill yourself or we will kill you.");
ctx->where = CLEANUP;
ctx->times_called++;
return 0;
cleanup:
puts("But Chud, you cannot do that, it's not safe for our democr-AAAAAAAAAACCCCCK!");
ctx->times_called++;
return 1;
}

int main() {
struct tranny_acking_context ctx = { .where = INIT };
while (!eventually_ack_all_trannies(&ctx));
printf("Calls needed to ack all trannies: %d\n", ctx.times_called);
}

There you go, no inline assembly used.
>>
>>107236508
The internet was a DARPA project. Onion routing too. DES too.
>>
>>107235840
>They're obsessed with being "marginalized" and "excluded".
Actually that's Cniles. Cniles reject ideas like modules, good macros, FP, OOP, and generics, and everything else invented in the last 50 years of programming because they want to be "marginalized" and "excluded". It is the rest of the world that is wrong, according to Cniles. Rust programmers are really happy about Rust becoming mainstream, just like Lisp programmers were happy about Lisp machines, and Pascal programmers were happy about Pascal's popularity in the 80s and 90s.
>There's nothing more satisfying than entering a thread where people are talking about Rust while ignoring the screeching Rust users. It inflicts real emotional harm on them.
You're projecting again. This whole thread is Cniles screeching and lying because people like Rust. Cniles are emotionally harmed because people they don't even know who work at software companies are writing better code by using a better programming language. Windows and Android getting faster and less buggy is supposed to be a bad thing, according to Cniles.
>>
>>107236543
I'm not reading this mentally ill post. Sorry.
>>
>Windows and Android getting faster and less buggy
>>
>>107236510
So, when was last time you went to the church? Have you prayed to your nigger loving pope yet?
>>
>>107236583
That was too easy.
>>
>>107236571
>Linux wasn't slow or buggy to begin with.
>>
>>107236598
>Linux out of nowhere
>>
>>107236534
That's just a state machine. You haven't actually shown any coroutine behavior in this post.
>>
>>107236327
>Who cares? It was designed 40 years ago and it stuck because sometimes it's convenient. If you don't like it, don't use it.
BASIC, FORTRAN, COBOL, Lisp, Algol 68, PL/I, Pascal, and all the other languages did not have that kind of bug, and these languages are all older than C.
>>
Genuinely, if I don't know either of these languages, which should I learn if I started right now?
>>
>>107236662
Rust. It will make you think correctly when you're inevitably forced to work on C++ dog shit.
>>
>>107236534
>[INIT] = &&init,
>goto *jump[ctx->where];
That's not even C.
>>
>>107236639
I implemented what you asked me to.
>>107236701
Works on my C, tranny.
>>
>>107236540
From a long past time where it was actually relevant.
Nowdays DARPA is just some cultural war bullshit and running a daycare for "marginalized groups".
>>
>>107236540
sudo too ironically. something that made zogduke tards with their "but muh GPL" go speechless >>107209556. lol.
so
the real world: a rust project actually replaced a darpa project
the real world: rust (both language and impl) has nothing to do with darpa
the real world: ZERO trannies (or jeets ;) ;)) in the rust lang team
the jeet hasbara world: whatever their brains are defecating this non-shabbat day of the week
>>
>>107236731
>Works on my Ctranny.
Your Ctranny doesn't follow the ISO standard.
>>
>>107236660
That's cool, you are free to use those as well.
Do something.
Show that you can build something.
>>
>>107236757
I don't follow ISO standards by choice, you can't follow ISO standards because you're a tranny freak for whom a spec was never written in the first place.
>>
>>107233898
>HOW DARE YOU HAVE FREEDOM?
Brought you by the same people that want the freedom to cut their own dicks off and then join a statistic.
>>
>>107236765
>you can't follow ISO standards because you're a tranny freak for whom a spec was never written in the first place.
My favorite languages all have ISO or ANSI standards, but nice projection. You post code that doesn't follow the ISO standard and isn't even real C, but somehow it's my fault.
>>
>>107236752
sudo is absolute dogshit!
It is a bad practice. You should not use sudo, no matter in what language it is written in.
The concept of entering your user password once and then everything in the console can do shit as root for a temporary duration, is idiotic and crazy!
>>
>>107236881
Okay tranny, I have deadlines and I don't get paid to worry about what's standard or not.
Richard Stallman is the only authority that I have and his compiler compiles this C code just fine.
>>
>>107236885
that's not how sane people use sudo dumb retard.
>>
>>107236900
Because sane people don't use sudo at all.
>>
>>107236885
it's dogshit also because of the overly complex policy language features 99% of users never touch.
>>
>>107236752
Holy shit, didn't even know about this. Cniles on suicide watch
>>
>>107236900
It is how sudo is used by default by fucking NSA contractor RedHat!

What you have to realize is that you have to use your own brain and should stop claiming that something is good because a government, a defense contractor or a spy agency tells you it is good.
All those government adjacent organization have a history of producing lazy dogshit, because they have neither accountability, nor a competition in a market.

sudo is insecure.
It always was.
Rewriting something that is, by principle, insecure, into rust, so that you can be insecure while running rust, is dumb.
>>
>>107236534
why would you use computed gotos instead of a switch statement? this code is so fucking retarded.
>>
>>107236959
seethe
>>
>>107233461
They are also being financed by Microsoft, Amazon, Meta and Google to do so - jewish big tech filled with 3rd worlders.
But then you are the jew or jeet for calling them out.
Check out the rust foundation website if you wanna see for yourself
>>
File: ok.jpg (375 KB, 1024x863)
375 KB
375 KB JPG
>>107236992
>Check out the rust foundation website if you wanna see for yourself
Yawn.
>>
>>107228535
We have this song though. jsissies only have jeetpack and a shitty UI library written by facebook.
https://www.youtube.com/watch?v=H4YRPdRXKFs
>>
File: 1735625797253.png (38 KB, 869x292)
38 KB
38 KB PNG
Reminder that rust developers seriously rewrote pic related, and those super smart people NEVER considered that MAYBE this is a bad thing, no matter in what language it is written in.

I understand it when a user doesn't grasp the risks of sudo. He just does what he learned and what everbody else is doing.
But someone who rewrote sudo line-by-line in a different language, surely has to learn all the lunacy that comes with it.

But nope... the government adjacent foundation doesn't pay us to think!
They pay us to rewrite, so we rewrite!
>>
File: 1742538818432.png (84 KB, 1135x667)
84 KB
84 KB PNG
>>107237062
Meanwhile lets try the same thing with run0, which is an actual replacement of sudo where the developer turned on his brain and realized that sudo is inherently bad.

aaaand... it asks for a password again and doesn't let any random user-run script hijack root just because it was run after a sudo command...
>>
>>107237062
There is nothing wrong with this. sudo authenticates you're running code on the correct and authenticated pty. Don't use tmux or some shit and use a modern Linux kernel that disables TIOCSTI and it won't hurt you.
>>
>>107237128
Different auth philosophy. I agree in principle that dbus+polkit is a better place to auth than relying on weird POOSIX boomerisms of setuid binaries and pty authentication, but I don't really think it's necessarily better. You shouldn't run random shit that will call sudo in your terminal you just ran sudo on.
>>
>>107237062
What were you expecting from agents of entropy literally called "rust"?
>>
>>107237150
It pretends that you are running things as user even thought that you obviously still have root rights.

Go ahead and tell people that "sudo command" doesn't actually mean that only that command is executed as root, but that actually your whole fucking pty gets root for quite a long long time.
If the pty gets root rights, THEN WHAT THE FUCK IS THE POINT?, just do su - root then, then you know exactly which console has root and which one doesn't, no fake bullshit.
>>
>>107237177
It is the philosophy of not lying.
>>
>>107237177
You should run su, like everybody always did.
sudo was always considered as insecure and i am old enough to remember the time when linux wikis had a big huge warning telling you that sudo makes things more convenient, but to a huge trade-of and that you shall not use it on any important environment.
>>
>>107237212
I don't really agree.
sudo at least has use_pty, prior to Linux disabling TIOCSTI by default, so your terminal could be hijacked.
>>
>>107237199
lying about what though? I don't understand what the problem is. I agree that setuid is weird, a lot of high profile security issues with sudo is around its dependence on strange POSIX-isms, but it is what it is.
>>107237188
I mean, if you feel that way, you can disable credential caching for the tty.
>>
>>107236959
real C code would look closer to this.
#include <stdint.h>
#include <stdio.h>

struct tranny_acking_status {
const char *msg;
};

const struct tranny_acking_status INIT = { .msg = "Starting to kill trannies..." };
const struct tranny_acking_status IN_PROGRESS = { .msg = "No, Timmy, trannies are not yet dead..." };
const struct tranny_acking_status NOT_YET = { .msg = "Yes, Timmy, we're almost done..." };
const struct tranny_acking_status ALMOST = { .msg = "Okay tranny, you have an option to kill yourself or we will kill you." };
const struct tranny_acking_status YOU_MAY_ACK_NOW = { .msg = "But Chud, you cannot do that, it's not safe for our democr-AAAAAAAAAACCCCCK!" };

const struct tranny_acking_status* ALL[] = {
&INIT,
&IN_PROGRESS,
&NOT_YET,
&ALMOST,
&YOU_MAY_ACK_NOW,
NULL,
};

int main() {
size_t curr = 0;
while (ALL[curr]) puts(ALL[curr++]->msg);
printf("Calls needed to ack all trannies: %zu\n", curr);
}

(i don't miss C. back to rusting...)
>>
>>107236926
interesting. can you provide specifics and comparisons with other similar tools, and how they do things separately.
>>
>>107237305
Way to miss a point retard, now modify your code to include a call to function x during ALMOST state, oh wait, you cannot because you're a dumb troglodyte that removed the whole point of abstraction.
>>
>>107237253
>a lot of high profile security issues with sudo is around its dependence on strange POSIX-isms,
I love it how you kinda want to shift the blame on POSIX or on imaginary boomers with old practices, while those were same old practices tell you to just use su and did so for decades.

sudo was created (as a DARPA project, as we learned now) to break those concepts.
sudo got popular at a time when Windows rolled built their UAC.
The concept, that a user should get temporary root by a simple confirmation, was the hot thing for DARPA.
2006 Windows Vista introduced the UAC
2004 Ubuntu was the first distribution to include sudo per default.

Reminder:
sudo got first created in 1980!
It took 24 years for it to get included in distributions!
Because during those 24 years, everybody always knew and told you that the concept of sudo is dumb and that you should only use it on some test machine you don't care about.
>>
>>107237360
>how dare you insult my spagetti abstraction
>>
>>107237378
I was asked to write a spaghetti abstraction, so I did, because I can, still less lines than equivalent in Rust.
>>
>>107237253
99.99 % of users believe that sudo only runs one command as root.
I that's a favorable estimate, in reality it wont be 1 in 10k, but more like 1 in 100k or a million, who actually knows about the lunacy that is sudo.

It is called: Lying by omission.
>>
>>107237394
dumb retard. with my shit 2minutes code above, you could easily add a callback (function pointer) field alongside msg, which is what any actual coder would have easily deduced. this is why it's a struct not just straight strings, so anyone with a single functioning brain cell can fill in the trivial gaps.
this retarded triviality doesn't even need to be spagetti in C.
as for rust, it's is a league of its own (in the system language landscape), and no one non-tard would even try to claim otherwise.
got it tard who never wrote real functional code in his sorry life?
>>
>>107228548
By your logic Java (or Kotlin) shouldn't be a mainstream language and yet here we are, one of the most used backend programming language in business.
>>
>>107237510
Wait nvm your logic is sound. I fucked up lol. I'm too stupid for Rust :)
>>
>>107237478
And what if those callbacks all need to take different arguments?
>>
OpenBSD guys rewrite sudo:
>we wrote our own tool that has none of the bloat, is 99.83 % smaller than sudo and therefor more secure because the amount of critical code is kept to a minimum
>we know that sudo is insecure by design, but we can make it as secure as possible
Poettering (literally a Microsoft plant) rewrites sudo:
>we already have a PID 1, and sudo isn't just boated and insecure by design, but its also an SUID binary, you don't need SUID if you are on PID 1 already, therefor reducing the threat vector even harder
Rust troons rewrite sudo:
>sudo is perfect! We need to rewrite the exact same thing, including ALL its flaws, but in a language that catches use-after-free on compile time (if not wrapped in unsafe{}, which we use extensively)!
>>
>>107237608
you pass a context type, erased to a void* if needed.
have you never seen the API of a C library that uses callbacks?
of course you didn't.
>>
>>107237658
Yes I seen billions of them, and they're all garbage.
>>
I still don't understand this C fascination. I can partially understand C++ holdouts, but C cucks should have been rolled into C++ or Rust by now.
>>
>>107237742
Cniles are too mentally ill to pass -fno-exceptions -fno-rtti into g++
>>
>>107235563
If you are not mentally ill, why are you here?
>>
>>107234842
>talking about Lisp
>randomly brings up brust again
Absolutely buck broken
>>
>>107237742
c++ is the ultimate retardation.
it's THE FILTER that predated rust, except it worked backwards (anyone who did as little as giving it a look is out).
the majority of sane system programmers already moved from c straight to rust, but will still have to maintain c code for years to come. some got overwhelmed by the disparity in dev experience and abandoned c for good, but not many.
all the "muh C" vs "rust them" is a /g/eet nocoder sport.
>>
>>107238062
top kek, I went C - Rust - Rust went to absolute shit so I went back to C - C++ to do some modding
I hate cargo so much bros
>>
>>107238140
>Rust went to absolute shit
when did that happen and specifically how?
>>
>>107238230
I'm really not interested in getting into it because I've seen that "point by point refutal trolling" that modern Rustists do compulsively.
Suffice it to say I just liked the earlier developer community and development direction better and then enough churn happened that I'd have to relearn everything.
I left around 1.4.0.
>>
>>107234860
You said it yourself, rust performs better.
Also it has a much nicer ecosystem imo.

And lastly it supports way more targets, from microcontrollers to web.
>>
>>107238353
Well don't be surprised by point to point refutals when you keep spewing myths and bs about it.
It is not trolling it is defending your position.
>>
>>107234874
It's ABSOLUTELY filled with browns. Try talking shit about Muslims, and watch the ban.
>>
>>107238798
Like clockwork, dumb little rust bitch
>>
>>107234117
brother, stop huffing copium. it isn't good for you.
>>
>>107238894
post code in any language
>>
>>107238230
Since the other anon doesn't want to waste his time with a cultist who lies, let me go for it:
The async / await in Rust is complete and utter garbage, that got only added to check a box on a list, and is ridiculous.
>>
>>107240087
async/await is both great (although some features required nightly for a while), and you don't have to use it, as it's trivial to go from async to sync and vise versa.
only reply with code.
>>
>>107238140
That's the story of most people who decided to try out Rust, to see what all the shilling is about.
Mine as well.
You realize that the language is a playground of bad practices, that LARPs as system language and then comes with its own npm rip-off and dependency hell.

There is a reason why there are almost no noteworthy projects written in Rust out there - and why the ones who do exist are either auto-converts or experimental and unstable.
>>
>>107240132
>you don't have to use it
That's like saying that i don't have to use cargo

In practice, this means to just not use Rust.
>>
Rustrannies can't meme so badly
LMAO
>>
>>107240161
>didn't reply in code
surprise surprise
>>
>>107228426
Everyday you cope and seethe over rust being adopted more and more
>>
File: 1761521103855405.jpg (33 KB, 500x443)
33 KB
33 KB JPG
>>107233219
>frogpost
>shitpost
Every time.
That said, I cannot disagree that this garbage thread is awful. Too many such cases, but anons created this mess with their shitposting dependencies and pot-induced dementia. Many of us warned about going overboard, but they don't care.
>>
>>107241294
its not being """"adppted"""""" its bei ng FORFED
>>
>>107228426
If I might add, Fil-C; a memory safe dialect exists and already has its own linux variant for you to use.
>>
>>107228827
>I'll never have to deal with jeets.
I am Indian and I will learn rust from now :)
Programming languages are easy to learn for high iq indian brain like me
Its funny how low iq niggas here think its rocket science or something
>>
Listen up, cargo cultists.
Every time a Rustacean waddles into the room with their “b-b-but the borrow checker keeps me safe” energy, a C++ dev somewhere wakes up from a 3-day compile-fueled bender, downs a liter of coffee, and manually inlines a template just to assert dominance.
Rust folks be like: "My compiler yells at me until I write perfect code!” Bro, my C++ compiler doesn’t yell at me — it writes ancient runes in red text across the terminal and challenges me to mortal combat. You think you have strictness? My build system once summoned a segmentation fault at compile time.
And don’t even get me started on features. Rust bragging about ownership like it invented the concept. C++ invented ownership back when Rust was still deciding what color its crab mascot should be. Meanwhile Rust’s over there chanting “no nulls, no data races” like a cult mantra while C++ devs are juggling raw pointers blindfolded and somehow shipping AAA games, kernel drivers, and missile guidance systems before lunch.
Rustaceans: “Memory safety should be guaranteed!” C++ devs: “Memory safety is guaranteed… if you’re good.”
The Rust community really said “Let’s make a language that protects developers from themselves!” Meanwhile C++ devs are like “If my program crashes, that’s a skill issue — for me or the CPU, we’ll find out.” You can keep your Option<T> and your Result<T, E> hand-holding. C++ has std::optional and std::expected too — we just don’t brag like we invented oxygen. And yes, our error messages look like the Dead Sea Scrolls written by a compiler possessed by Cthulhu. That’s not a bug. That’s lore.
Rust fans: “But we have cargo!”
That’s cute. C++ has like fourteen build systems and none of them are good, but we use all of them anyway because chaos builds character.
At the end of the day, Rust is great…
But C++ is what your Rust compiler is written in when it wants to feel fear again.
>>
>>107229449
i thought it was common knowledge you had to still use a format string for literally any string you pass to printf not known statically

printf("%s\n", buffer);
>>
>>107237742
I mainly use C because it has unparalleled support. Every ecosystem imaginable has a C compiler and if all of it vanished overnight, any dickhead can still make a C compiler in their basement and support pretty much all of C99 with little issue. The same cannot be said about C++ since the spec is massive even if you stop at C++11. That simplicity, robustness, availability and immortal legacy appeals to me even though the language itself is flawed. But if I didn't value those things, I'd just move on to odin.

C is also just a very productive language in spite of its age and I don't really feel like I'm missing much not having access to C++ features, with a few exceptions like overloading.
>>
if rust is so good, why does nobody use it?
>>
>>107233219
No AI is this retarded. It's natural stupidity.
>>
>>107237478
>you could easily add a callback (function pointer) field
Why add pointless runtime overhead? C++/Rust don't need this bloat.
>>
>>107245105
It's difficult to use properly.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.