Why does anyone use this bloated shit?

>>105959029 (OP)
>what is static linking
statically linked C hello world is around 800kb
statically linked C++ hello world is around 900kb
statically linked Rust hello world is around 2mb
At least let's be frank abou tit.

>>105959029 (OP)
No way that is real, the Rust one must be static linking all libraries.

>>105959029 (OP)
Remove stdlib

>>105959029 (OP)
Delete System32 that'll free up some ram.

>>105959029 (OP)
A proper comparison would use puts, not printf retard

>>105959029 (OP)
link rust against stdlib and call printf

>>105959029 (OP)
Did my own testing

>>105959597
nubmers are falsisfed rust would be in gigbabytes

rust and go hide nsa telemetry code in their binaries that's why a simple hello world is 4MB, it holds an entire tcp/ip client in there and that was the most they could do to compress/hide it.

>>105959597
What is that exec time

>>105960177
I doubt that.
Go does have a whole garbage collection/runtime thing in there though.
Rust is more of a WTF, it can’t even go toe-to-toe with golang. And they tried to get this inti the linux kernel? Even stdlib can’t abide in there.

>>105959597
>>105960112
>>105960199
btw the program calculates the first million prime numbers without calling printing functions.

>>105960270
So it's a no-op or comptime calculated in C and C++.
Why are there so many "people" who post benchmarks that are like this? It's frustrating to deal with your ignorance and resulting misinformation.

>>105959597
Golads I...I kneel...

>>105960357
If it's calculated at compile time then why is its compile time shorter than Rust's compile and run time both?

>>105959029 (OP)
wc is a retarded measure. At least use size.

OK, did another testing.
Code is here: https://sharetext.io/dd3d7e60

>>105959029 (OP)
noobs

>>105960544
someone test nim

>>105959029 (OP)
this thread again
youre undermining our authority with fals assertions, lad
a while ago a crab showed that you can make a hello world smaller in rust than in c
idk why it would matter anyways
unless you wanna fit a program in a qr code or something

aaa speaking of the wolf
>>105960571
like i stated
doesnt matter
your language still smells like frutti di mare

>>105959029 (OP)
C is indeed better for the purpose of writing a hello world program.

>>105960678
mfw
jk
its not without reason its used as a didactic tool
and its what i love about it
its simple

The fuck are the command like arguments doing?

>>105959029 (OP)
I suppose the Rust version actually includes the fucking code you need to run the program, as opposed to having to dance around retarded ganoo licensing autism and dynamically link in 2k25.

>>105961017
Why would anyone want that?

>>105961030
the zoomer computing world just loves redundancy and containerization

>>105961030
Why would anyone want to make sure a program just fucking works? Neverminded, a freetard wouldn't understand.

>no namespaces
>abhorrent preprocessor
>no generics
>null terminated strings
>undefined behavior
>no lazy iteration support
>no closures

>>105961061
I'm beginning to think you are monstrous homosexual.

>>105959029 (OP)
>It's another thread of fa/g/g/ots whose jobs are mostly to design and produce unholy abominations in Electron and other satanic frameworks, complaining about bloat on /g/
Enough already, you're insufferable

>>105961214
Your mom has had other people's dicks in her mouth.

>>105961214
Electron is unironically based as fuck. It makes the freetard seethe by bringing useful software to his meme system.

>>105961235
Not my business. And even then, at least I don't waste my free time bitching about shit I'll never put into practical use
>>105961245
>Electron is unironically based as fuck. It makes the freetard seethe by bringing useful software to his meme system
t. nigger cattle

>>105961245
Your mom was a second dad who spent too much tubby time with you.

>>105959029 (OP)
>cnile retard discovers static linking
https://en.wikipedia.org/wiki/Static_library#Comparison_to_dynamic_linking

>>105961258
C programmers are a national treasure. Rust is a Biden administration scam, like solar panels in Maine.

>>105961278
>C programmers are a
You are a 70 IQ pajeet LARPing as a cnile. Worst of both worlds. You will never be a programmer.

>>105961278
Or social workers on police forces. Or boys in girls sports. Or equity and inclusion in the c-suite. Or electric cars anywhere. Or mrna vaccines for the common cold. Or Haitian 24 year olds in your 12 year olds classroom.

Just another attempt to infiltrate and break working things that don't need leftist fags messing them up.

>>105961249
>>105961257
While extremely simple, spotting the common freetard (idiota libera) in the wild is truly an amusing activity for beginners and experienced hunters alike.

This thread is another example of why cniles are caged monkeys with no relevance in real world. Actual programmers see this picture and spot the mistake in 1 second. In HN/LinkedIn you would get laughed out of the room.

While the nocoders compare bloat without knowing the difference between static and dynamic linking and the overall irrelevance of comparing size in x86 platforms.

But I do admire the ingenuity of Rust. By taking slightly left-leaning political stance, they turned every single basement dwelling /pol/ nocoders into unpaid Rust shills. Not a single day goes by in /g/ where these nocoders aren't complaining about oh-so-called "failed"/"irrelevant" Rust. Don't see that happening for D/Nim/Zig/Odin. Point at them and laugh.

>>105961474
You will never be memory safe

>>105961065
Null terminated, Ascii strings are unironically the best way to do strings though. UTF8 sucks.
>inb4 you can't do non English chars
Maybe people who do not speak English should make their own programming languages and standards instead of begging the white man to include them?

>>105959597
>the only client side drawback of C++ is huge amount of RAM usage compared to C
No wonder its so widely used

>>105961474
Xir said they are all statically linked thoughbeit.

>>105959029 (OP)
>Complains about bloat
>Uses printf() when he could've used puts()
Pathetic.
>B-but __builtin_printf() replaces it with puts() anyway
Still bloat.

>>105961326
Works on my machine.

>>105961474
>HN/LinkedIn
Dunning-Kruger midwit spotted.

>>105961538
Not an argument. JavaShit is even more widely used.

>>105961534
dude you're fucking retarded
I've been programming for over a decade. I've written more C than you. what the fuck have you done?
C is a dogshit language for new projects, simple as

>>105959062
> 800K
Skill issue. In my machine Hello world in C is 22016 bytes with full static linking. You must be retarded or something.

>>105961717
Your response makes 0 sense to the subject of my post. Meds.

>>105961694
And it's better

>>105961746
the subject of your post is not worth arguing, it's akin to arguing with someone over the existence of birds
I'm just making fun of you because it brings me joy

>>105961782
That ascii strings > utf8. Only an ESL Indian would argue this. Way you out yourself Sandeep.

AMDGPU crashes has red pilled me on C being a shit language. Reading the source code for AMDGPU makes me want to jump off a cliff. No wonder every single time a new Linux kernel feature is added, there are like 10+ CVEs. If Rust emits larger binaries but doesn't become CVE bait out of the gate, it already won.

>>105961755
I agree, JS is better than C++. I also prefer catshit over dogshit and AIDS over syphilis.

>>105961717
>I've written more C than you
Doubt.
>I've been programming for over a decade
Jeets can do something for 30 years and still never get any better at it.

>>105961846
why woukd you prefer cat shit and aids. Im cured of my siphylis.

>>105959062
The great thing about C is there are 100 compilers and 50 libcs:
$ musl-gcc -std=c23 -Os -Wall -static -o hello helloworld.c
$ du -h hello
20K hello

C wins again.

>>105961841
>>105961258
>>105961065

>>105961846
>hates JS
>I also prefer AIDS over syphilis.
Most logical JS hater of the year

>>105961841
Rust includes unsafe, which makes it memory unsafe. Rust drivers are absolutely full of unsafe, to the point that it's basically just C but with 200% more stupid line noise and 800% more binary bloat.

>>105959029 (OP)
well its named Rust, why woould you use a language with that name? nigga, they are spoiling you from the begining, nigga, run, dont use Rusted

>>105961961
I didn't say I prefer having AIDS myself. I prefer fags getting it.

>>105961718
Go figure, 22KB and is still bloated.
The glowies behind rust must be complete idiots to need 2MB for all their spyware crap.

>>105961903
yeah i love getting to choose between forced dynamic linking and my program being slow as balls

>>105962013
Works on my machine.

>>105961474

>>105962013
You can static link against glibc if you don't use anything that pulls in NSS. libc is a heap of locale-dependant garbage anyway, so you shouldn't be using much more than mem*() stuff and printf(), unless you're a brainlet. Rust toddlers don't even code, so they can't comprehend not having 900 dependencies before they even write hello world.

>>105961984
Rust also has basic high level features that C++ has, like for each style loops, abstract data types and more... I literally debugged an AMDGPU crash that was because some code didnt loop terminate correctly because the loop counter != Number of elements being worked on because C is literally that shit. So of course the loop counter off by one'd some buffer and crashed the kernel because thankfully redhat added something like FORTIFY_SOURCE to Linux. in rust or c++ this wouldn't have happened because those languages have basic iterators that enable stuff like for each style loops. No need to do the hoare logic on your loops, when it's constrained by your container for you.
You're a delusional retard if you still defend C or you literally do not write software.

I also remember when QEMU got a massive performance improvement in plan9 fs driver because they used glib hashmaps instead of some O(n) algorithm. In the advent of cope threads, cniles literally do not use hashmaps because they're too proud to admit having basic generic containers and data types is actually a good thing. Just admit that C is outdated and stop trying to fucking cope like a dumb cuck. This ha nothing to do with memory safety and everything to do with C just being shit.

>>105962079
Sounds like a skill issue.

>>105962101
>Sounds like a skill iss--Segmentation fault: core dumped

>>105959029 (OP)
why is this that way? what is rust packaging into it that c doesnt?

>>105962127
Read https://github.com/johnthagen/min-sized-rust

>>105962079
You can write a good, quadratic probing hash table in less than 100 lines. 100% of people doing AoC are brainlets. Competent people don't waste time on childish shit like that. Cnile brainlets struggling with the language being barebones and Rustard brainlets struggling with other stuff doesn't really prove much ,except how low your standards are.

>>105962156
That's some high quality copium right there.
>Compress the bloated binary with UPX
lmfao. Rustoids are cooked.

Windows hello world is 4kb (can be less if you fiddle with linker settings) and shows an actual graphical message box instead of your gay command line bullshit
Linux = bloatware

>>105962158
Or you could use a nonshit language like C++ or Rust and have swisstables that work genetically over any hashable data structure.

You "C programmers" are so out of touch with reality.

>>105961903
With -s it's 14K.

>>105962191
>genetically
I assume you mean generically. Tell me which aspects you think should be generic and I'll debunk them all.

>>105962191
>a nonshit language like C++
lmao. Thanks for the laugh, anon.

>>105962158
>ye I'm going to implement my own hash table
and all of a sudden you have no standard agreed upon between libs for hash tables
it's incredibly obvious that you have not actually produced any significant software
just because you can implement a single data structure does not mean shit

>>105962158
>100% of people doing AoC are brainlets. Competent people don't waste time on childish shit like that.
Did you get filtered by the numpad problem? It's ok anon. No one will know.

>>105962252
It's definitely nonshit compared to C.

>>105961670
>bro the real engineers seethe about rust in 4chan bro

>>105962256
>and all of a sudden you have no standard agreed upon between libs for hash tables
So what?
>you have not actually produced any significant software
I've produced vastly more than you. I'm not arguing in favor of C because I think it's a good language for new projects. It's just that your arguments against it are retarded and indicative of a mediocre spastic, who's been collecting paychecks for gluing other people's libraries together.

>>105962261
0/10 bait. I pity you.
>>105962285
>It's better than a 50 year old glorified assembler.
Is that really how low the bar is?

>>105962313
>I've produced vastly more than you
have you?

>>105962313
No you haven't and if you have, it's probably as shit as the Linux codebase that's full of CVEs yet to be exercised. If even the most premier open source C codebase can't deliver new features without exposing a new hole, neither can you. I don't give a single fuck what bullshit cope you claim, you literally cannot and only flew under the radar because no one cares about (You).

>>105962336
Yep, filtered. Many such cases. A C cuck will never be a real programmer.

>>105962340
>have you?
Yes.

>>105962371
really?

>>105962342
>I haven't seen it, but it's probably just like the fictional code I dreamed up in my unmedicated schizo dreams.
Very compelling.

>>105962385
>Hurrr, this slop will blow his mind.

>>105962397
see if you can point out the novel feature of my language

>>105962158
>>105962191
>>105962252
>>105962336

>>105962342
Just give up. Nobody with a sane mind wants to code in rust.

Learn to flags

https://github.com/johnthagen/min-sized-rust
https://mainisusuallyafunction.blogspot.com/2015/01/151-byte-static-linux-binary-in-rust.html

>>105961984
>Rust drivers are absolutely full of unsafe, to the point that it's basically just C but with 200% more stupid line noise and 800% more binary bloat.
False

>>105959029 (OP)

Who fucking cares about the size?
Storage is cheap as hell.

>>105963223
>he doesn't know that executables are loaded into RAM

>>105963328
Dynamic libraries are loaded into RAM as well...

>>105963369
>Dynamic libraries are loaded into memory once and shared among multiple programs that use them. This reduces disk space usage and allows for more efficient memory management.
https://kaksha-dev.github.io/c/static_libraries

>>105961903
>The great thing about C is there are 100 compilers and 50 libcs:
>unstandardised toolchains good

>>105959029 (OP)
$ musl-gcc -static -nostdlib -fcf-protection=none -fno-asynchronous-unwind-tables -Wl,-z,noseparate-code -Wl,-z,nosectionheader -xc - -lc <<!
#include <unistd.h>
void
_start(void) {
static const char s[] = "Hello, World!\n";
write(1, s, (sizeof s)-1);
_exit(0);
}
!
$ ls -l a.out
-rwxr-xr-x 1 anon anon 487 Jun 18 14:30 a.out
$ ./a.out
Hello, World!
$

>>105963486
the standards are well defined and supported, for the benefit of compiler makers

>>105963802
>well define
hahahahahahahahahaha

>>105963802
>well defined
(You)

>>105962340
>.unwrap() everywhere
handle your errors you nog

it's honestly pathetic that much of /g/ dislikes Rust. it's a fucking incredible language. there are some problems with it, but it offers Clojure-esque data transformation in a systems language. the most important part of any programming language is its data structures and abstractions over them, and Rust has this very figured out. I do wish Rust had a "association" trait so that BTreeMap, HashMap, and Vec could share some methods.

>>105963831
>>105963838
undefined behavior is good both for maximizing portability and minimizing work needed to meet the standard which is why any jackass can make a C compiler with at least iso99, or ansi in a worst case

meanwhile a full spec C++ or rust compiler is a nightmare

>>105963862
those conditions are impossible to reach according to my understanding of the code, hence I do .unwrap() for them. learn the basics of differentiating errors arising from external input (where you return an error) vs errors arising from a buggy implementation (where you crash hard).

>>105959029 (OP)
The niggers at the /g/ telegram group are seething about this btw

total troon death btw

>>105963924
>learn the basics of differentiating errors arising from external input (where you return an error) vs errors arising from a buggy implementation (where you crash hard).
you should be handling errors in either case, or at least using .expect(). it's not just for recovery.

>>105963328
It's 2025. You should have at minimal 32GB of RAM.
3.5MB is like 0.0001% of your main memory.

>>105964002
it's <any year>. you should optimize algorithms and data structures to run as performant as possible as according to our understanding of physics and circuitry.

>>105963987
nigga a string in .expect() isn't going to help me at all when debugging my shit
>hurrr I need a paragraph describing the issue that arose

>>105964014
A statically linked executable, like those in Rust, tends to be more performant than using shared libraries. Optimizations such as loop unrolling greatly improve the performance but may also increase the binary size.

>>105960616
And then a cnile showed he can make a hellow world even smaller @<400B

And then, an MC tard showed that I can make a Hello world in 76B on i386 linux elf, without even trying and that this debate is gay.

>>105964002
Retard take.
>>105963913
True and real.
>>105964295
The more bloat the easier to hide malware there.

>>105961474
TRVKE

>>105959029 (OP)
only 500KB in my machine
$ cat hello.rs
fn main() {
println!("Hello, World!");
}

// Local Variables:
// rust-indent-offset: 2
// End:
$ rustc hello.rs
$ wc -c hello
505016 hello

>>105964037
https://www.youtube.com/watch?v=FsRfPcJaR5U

>>105959029 (OP)
>22KB is good!
string + syscall + some technicalities to return... hello world needs a few dozen BYTES tops.

>>105962928
> 1% unsafe code
This “analysis” is bonkers.
It’s likely that most, if not all, of code that was not marked as unsafe was also likely intrinsically safe in C.

>>105964800
>intrinsically

>>105959597
GO GODS... I KNVVL

>>105964844
>has an entire HTTP server in its stdlib
>no sets
lmao

>>105964849
>sets
bloat, all you need is map[int]struct{}

>>105964854
ok now do an intersection of b-tree sets with map

>>105964861
>can't merge maps
filtered

>>105964864
you don't even know what a b-tree is used for
that is how retarded you are

Also, obvious no coder opinion bringing up some bullshit academia problem. In reality, the Go map is 99% good enough and you never need more. Can't be bothered to write a 4 line for loop? Not my problem, get the fuck out and don't pollute my language with your garbage

ok now show me how it runs on an embedded system with RTOS requirements

>>105964873
>YoU dOnT eVeN kNoW...
All I need is a contiguous block of memory and an for loop and I gurantee my shit is faster, simpler, and took 5 minutes to write compared to whatever shit you spew out

>>105964884
>all i need is these constraints i can't get because i'm retarded and don't know how heaps work
l o l

>>105964905
>he thinks a b tree will save him in the interview
LMAO ok buddy, I'm sure they care about how you can do what chatgpt can in less time and less bugs, than working with a SQL DB because you never write a B tree yourself but use them indirectly with other tools. Dumbass

>>105964914
>saar my chatgpt saar

L O L. you are doomed, larping jeetoid. what's it like not knowing how to solve a single problem with your smooth brain, reliant on info you can't even validate? kill yourself and reincarnate as something less poo-comprised.

>>105964854
>>105964864
>>105964879
>>105964884
>>105964914
once again
>have an entire HTTP lib in stdlib
>no sets

>>105963929
yes, yes we are.

>>105963929
>/g/ telegram group
dear God

>>105961984
>The majority of bugs (quantity, not quality/severity) we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory (not that rust can catch all of these by far), error path cleanups, forgetting to check error values, and use-after-free mistakes. That's why I'm wanting to see Rust get into the kernel, these types of issues just go away, allowing developers and maintainers more time to focus on the REAL bugs that happen (i.e. logic issues, race conditions, etc.)....
>But for new code / drivers, writing them in rust where these types of bugs just can't happen (or happen much much less) is a win for all of us, why wouldn't we do this? C++ isn't going to give us any of that any decade soon, and the C++ language committee issues seem to be pointing out that everyone better be abandoning that language as soon as possible if they wish to have any codebase that can be maintained for any length of time.
>Rust also gives us the ability to define our in-kernel apis in ways that make them almost impossible to get wrong when using them. We have way too many difficult/tricky apis that require way too much maintainer review just to "ensure that you got this right" that is a combination of both how our apis have evolved over the years (how many different ways can you use a 'struct cdev' in a safe way?) and how C doesn't allow us to express apis in a way that makes them easier/safer to use. Forcing us maintainers of these apis to rethink them is a GOOD thing, as it is causing us to clean them up for EVERYONE, C users included already, making Linux better overall.
https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/

>>105961474
Looks like this thread really riled up the glowies.

>>105963886
There are people on this board who hate TypeScript and think JS is better without types.
It's midwits who are too retarded to understand anything more complex than basic imperative statements. They have never worked on anything remotely complex.

>I do wish Rust had a "association" trait so that BTreeMap, HashMap, and Vec could share some methods.
Iterator methods?

>>105964800
>This “analysis” is bonkers.
This is literally the author of that driver. He knows more about it than anyone.

>It’s likely that most, if not all, of code that was not marked as unsafe was also likely intrinsically safe in C.
Define "intrinsically safe in C"

Also why move the goalpost?
You claimed that:
>Rust drivers are absolutely full of unsafe
Which is proven false by the example of this driver.
Why are you moving away from your original point?

>>105964883
You don't need RTOS if you have async
https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown

>>105966029
>https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown
this is retarded
the autor is retarded
find a better article

the thing with an RTOS is that it performs in a predictable manner
not that its fast
also blinking a led? come the fuck on
the author deserves to be raped in a german metro for 38 minutes
>tweedegolf
fukken second wave? the site domain sounds gay and left wing asf

>>105966029
yeah
theyre complete globalist scum
'explains the incompetence

they dont need to be competent
they just need to be trustworthy

>>105966083
>the thing with an RTOS is that it performs in a predictable manner
And async doesn't?

>the author deserves to be raped in a german metro for 38 minutes
Your aggression and fixation on sexual degeneracy undermines your point.


Why do C programmers always talk about some weird fetishes when talking about programming?

>>105966130
doesnt change a thing to the fact the author doesnt understand what an rtos is about

>And async doesn't?
in theory you could
but its like trying to type while wearing boxing gloves
youre using states with async.
so you need to keep track where your async functions stopped


>Your aggression and fixation on sexual degeneracy undermines your point.
no, i just learned about that story two days ago and find the circumstances of it utterly hilarious
google it

>>105959486
GCC will optimize calls to printf by replacing them with calls to puts if they are equivalent.

>>105966167
>the author doesnt understand what an rtos is about
[citation needed]

>so you need to keep track where your async functions stopped
What do you mean?

>no, i just learned about that story two days ago and find the circumstances of it utterly hilarious
>google it
I don't see how your degenerate rape fantasies are any related to the topic at hand

>>105959029 (OP)
Because the size of a hello world doesn't factor into their ranking at all

>>105966192
>[citation needed]
the author himself

you didnt even read the article.
typical crab

>>105966220
>>[citation needed]
>the author himself
>pic related
non sequitur

>>105966228
no, its just that youre profoundly retarded, apparently
where does it state "repeatability"?
also the author just gives up on this point

typical crab
>find piece of advertisement
>repost it on 4 chan like if it was r*ddit

>>105966245
>no, its just that youre profoundly retarded, apparently
>where does it state "repeatability"?
I don't see how does this makes the image you have included in your post prove your claim that:
>the author doesnt understand what an rtos is about

>typical crab
>>find piece of advertisement
>>repost it on 4 chan like if it was r*ddit
You asked to:
>show me how it runs on an embedded system with RTOS requirements
So I showed you an article that describes how Rust runs on an embedded system with RTOS requirements.

Why are you constantly trying to move the goal post from your original point?
Why are you constantly trying to resort to ad hominem when faced with unexpected information.
Why are you talking about sexual fetishes out of nowhere?


It really puzzles me what makes C programmers behave this way. I wonder if this is some sort of defense or coping mechanism.
An inferiority complex perhaps?

Let's see how you respond to this post.

>>105966292
>I don't see how does this makes the image you have included in your post prove your claim that:
>>the author doesnt understand what an rtos is about
and thats why i say youre profoundly retarded becase its beyond obvious

an rtos' deal is repeatability, predictability
even afghani children playing in the desert sand know that
even the sentinelese people know that

>>105966318
>an rtos' deal is repeatability, predictability
And?

>>105966338
holy slow
>and?
and its not even mentioned in the comparison
retard nigger author doesnt test the ce ntral thing that makes an OS to be "RT"

in fact the obvious conclusion that async is retarded in an rtos is convenien tly shoved under the rug because "Embassy can't pre-empt running tasks, so it's less worthwhile to optimize this a lot."

no
he didnt do that because hes gonna have his latencies all over the place proving that async is not compatible with the whole rtos concept

>>105966372
>and its not even mentioned in the comparison
And?

>>105966415
wow
>mother of all slows
copey paste the convo into chud gpt
and ask him further clarifs
you have hit your free plan with me

>>105966422
you have hit your free plan *limits with me
try again in 24 hrs
you can upgrade to the pro plan for 1 ETH mothly

>>105966400
>he didnt do that because hes gonna have his latencies all over the place proving that async is not compatible with the whole rtos concept
He measured latencies. See https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown

>>105966422
>no argument
Like pottery

>>105964002
I mean I get you, OP is being a faget over trivial storage requirements for a file.
But that same mentality is why every damn program rapes your RAM now, why gamedevs make their games triple digit GBs, why specs for languages are absurdly complex, and so on.

>>105966440
>But that same mentality is why every damn program rapes your RAM now,
Modern software uses a lot of RAM because it includes a lot of bloat, not because it is compiled statically.

>>105966454
I didn't give a fuck about the OP point, retard.
I'm caring about the lack of care to optimization.
Big difference.
Lrn2read

>>105961017
Oh boy, you really want to play this game? Compiling with -static results in a 664K binary and the exact same performance characteristics.

>>105963700
God I love musl

>>105966434
*loud groans*
rare rust W
signs on the ground and in the sky indicate the niggers from ST (maintainers of smt32 ide) have jeet code in their compiler which emits suboptimal machinecode
when rusts relevant package is maintined by the community so is at the bleeding edge

stdatomic is a bunch of abstractions which provide no guarantees as to what the actual code will look like in the end
and so the way atomic operations are actually dealt with is implementation defined
which means the use of fallback routines, not optimized for the hardware
which probably means semaphores, mutexes and whatnot emitted in the smt32 code

the rest of the code is pretty much equivalent
rusts """"async"""" is actually "futures" which functionally are interrupts just with a different interface, from what i understand
and what else there is?

it wouldnt surprize me you dont even need to make the ops properly atomic because its a matter of writing data thats less wide than the data of your cpu
so that should be de-facto atomic
it is on x86

>>105965962
>This is literally the author of that driver. He knows more about it than anyone.
He also has more reason to frame it dishonestly than anyone.

>>105965962
>You claimed that:
No he didn't. That was me. You know there's more than 1 poster on here, right? Did you skip your meds today?

>>105963328
Ya, just like all your libc and other dependencies too.

>>105966029
Cope.

>>105966975
(in case someone reads this your data has to be aligned to 64 bits for it to work. so if you have a buffer of disparate types and a long in the middle straddling two 64 bit sections, its not atomic)

>>105967031
It's FOSS, you can check it yourself if you believe it's all just some conspiracy.

>>105963700
Gonna credit the source for that?

>>105967040
He directly responded to my response to you. It's safe to assume he is either the same poster or he shares same opinion. Otherwise he would say "NTA" or otherwise noted so.

And at the end of the day it doesn't matter if he is you or not. You claimed that:
>Rust drivers are absolutely full of unsafe
Which is proven false by the example of this driver.

That's all that matters.

>>105967063
What an excellent response from a C programmer.

>>105965105
Greg K.H. isn't a competent programmer. That was abundantly obvious when he made a dozen beginner mistakes on that readfile syscall he proposed a while back (and countless other times before that).

>>105965962
>Code isn't Safe™ unless a Rustoid has labelled it as such.
>If we wrap all of our unchecked and incorrect code with unsafe{} and then pretend we've audited it, that makes it magically Safe™
>If we only make comparisons with crusty, 50 year old languages Rust looks really good!
Fucking kek.

>>105967172
>It's safe to assume he is the same poster
Meds.

>>105961903
>>105959062
statically linked zig programs are 2kb

>>105959062
statically linked asm hello world is 235 bytes.

>>105966864
It doesn't matter when you lost the rights to your program.
I'm sure if you compile something that actually does something, the difference will be less. The OP pic is the same shit as jerking off over differences in web backends returning {"hello":"world"}.

>>105967341
Cope. >>105963700 is 487 bytes.

>>105967341
>>105967532
Ziggers on suicide watch.

>>105967506
>lost the rights to your program
That's not how that works, zoomer.
>I'm sure if you compile something that actually does something, the difference will be less
Holy copium.

>>105967547
>GNUtard being disingenuous about their licensing: episode 27394

Zig is even bigger

>>105967584
>t. Steve Ballmer

>>105963700
Can rust even get close to this? (And post proof?) I’d take even sub 5, or 10kb.

>>105967170
what is the source for that?

>>105967974
Permissive licensing won, GNU autism lost.
I hate Rust but the only reason why I like their rewrites is because they free software from licensing hell.

>>105967280
>>Code isn't Safe:tm: unless a Rustoid has labelled it as such.
>>If we wrap all of our unchecked and incorrect code with unsafe{} and then pretend we've audited it, that makes it magically Safe:tm:
[citation needed]

>>105959062
>>105967447
>>105967341
JS hello world is 20b

>>105968132
Yeah
https://mainisusuallyafunction.blogspot.com/2015/01/151-byte-static-linux-binary-in-rust.html

>>105959029 (OP)
My python version of this code is only 20 bytes...
Ohh well, I guess the Brahmin language wins again.

>>105968353
Sir, I kneel

>>105967532
>>105967537
You can use such compiler flags (which fuck up your program) with zig as well. I meant just standard zig build

>>105968309
27b*. Hello world in HolyC is 14b

>>105968152
https://desuarchive.org/g/thread/105627954/#q105629905