/tech/ - Technology

>>546
>Whenever we allocate an object, we do a quick check that we have enough capacity left in our chunk to allocate the object and then update the pointer by the object's size. That's it!
>THATS IT!
1500 lines of code thankyouverymuch
https://github.com/fitzgen/bumpalo


what a fucking garbage lang

c won

>>561
winning implies an actual fight.
when c just stepped over it

>>558
>>561
>>562
low effort gimmick award

>>564
its very telling that it doesnt take much effort to btfo rust

rust is tranny or something

rust rots your brain

c++ aryans won

I program in C++ professionally for 1 year so far. I tried learning Rust but aside the /g/ memes the syntax really is terrible. The language also depends a lot on macros and I never *got* the borrow checker so I just gave up. I don't see a reason to switch anyways since I'm comfortable with C++.
Also the niggers above me are the reason /tech/ fucking sucks, instead of derailing a thread just make a C/C++ one instead.

>>573
no mercy for rustrannoids doe
https://jonathancarter.org/2024/08/29/orphaning-bcachefs-tools-in-debian/

cancer lang for cancer redditors
the g meme is based on reality

Redpill me on rust.
Why not just write good C code?

The real use-case for rust is that it's an IQ test to keep out pajeets and niggers from programming.

>>584
because that wouldnt displace these awful c-huds from programming.
>>585
>a language created in such a way you can by-heart everything and include from cargo what you cant
mh hmmm.
training wheels are for accomplished profressionals, of course

>>584
on a more serious note-
people are seething at the fact that C doesnt hold your hand at all.
they show the miserable track record of linux' cves to support their claims.
linux is written by passionates, after hours.
they have varied backgrounds, expertise levels, and work on opposite sides of the globe. and that is asking for problems when using C.

problem is: when linux was started the choice was: either go C, or C++
and sepples would be a fucking mess to deal with bc of all the various abstractions. so LT went with C.

rustrannörs are gonna say you physically cant write correct, safe C code, but they ignore the fact that tons of critical infrastructure runs on C.
and the fact that webraisintery and os'es are merely a small fraction of all possible applications of programming, and that safety is not the slightest of concerns in most of them.

and also rust creates a new vulnerability to supply chain attacks because of its retard cargo system and the lack of interest of anybody in centralizing the most used crates into rusts library
heres the full list of dependencies to bcachefs-tools:
https://rpmfind.net/linux/RPM/fedora/devel/rawhide/aarch64/johnsonachefs-tools-1.11.0-1.fc42.aarch64.html

imagine having to audit all this raisin
and thats the reason nr1 nobody wants to deal with rust.

theres an easy fix doe, testament to the lack of imagination within the rust community as a whole
->just extract the live code, since youre working with sources
start with the main, and recursively get all the functions/methods/headers, paste into one fucking file for maximum laziness and viola
80% of the critique against rust in the kernel (by validity) could be disappeared with a fucking shell scrtipt
but out of the thousands of rustniggers
nobody had that idea
and obviously c-hads aint gonna write this raisin for the rustrannors bc rust is a filed project to begin with
and the community is human garbage

'umo

New Rust sissy on the right

>>904
HE HAS A FUCKING ANIMAL SEX TOYS COMPANY TRANS LOGO ON THAT LAPTOP

niggerlover thread ahoy

>>904
Apparently, a career where you do nothing but type is highly sought after by effeminate men. Who thought?

>>908
how were you able to recognize it?

>>1045
tsmt

>>989
>Who thought?
ESL Turd worlders such as yourself who take out gotchas from outlier rustrannies and apply it to what is basically a field dealing with logic as a whole. What a retarded question.