lmao... passing raw data and casting pointers everywhere, what a stupid language
but maybe... you feel smart doing so? TOP KEK
keep dealing with stupid low level errors kids while chads build real apps with real non toy languages
>b-but compilation time
yeah and debugging time is 100x longer in C LOL
>m-more portable!
on posix only KEK, pthreads don't even exist on windows while std::thread compiles and runs on linux, macos and windows LOL

>only dalit use low level language saar, only brahmin aryan may do the needful with Python saar

>>106167833
nice try rajeesh, we all know the curry street shitter is YOU

>>106167807 (OP)
> The zoomer cannot accept power and freedom even in his choice of programming language. Absolute servitude to a higher power is always his desire.

>>106167884
its about being efficient
good for you if you can afford to be inefficient and lose your time

>>106167807 (OP)
The c++ standard library is a bloated abomination. The C code generates substantially less assembly. I am all for cost free abstractions. But the standard library misses the mark.

>>106167884
I guarantee 95% of the people who actually program on /g/ are not writing anything that benefits from the "power and freedom" of C.

Rust has none of these problems. Truly rust is a language for the white man.

>>106167948
There are plenty of C/C++ programmers here. "Memory safety" is a meme that appeared inorganically 3-4 years ago and is completely uninteresting to people who have been using real languages for a living for decades.

>>106167807 (OP)
Damn, C really is king.

>>106167807 (OP)
sounds like youre seething, anon

>>106167807 (OP)
I know you don't know this, but Sephiroth programs in C.

>>106168020
even you admit it KEK

>>106168044
????
resetting an index is confusing to you, somehow?

>>106168057
it was a joke cause you're writing c = 0... your variable as the lang ... meaning c sucks ...
didnt think id have to explain that one ......
you killed the mood dude

>>106167807 (OP)
try to program a midi interface with some other shitty language, i dont give a fuck about your technical details and worries, i use C because its the most suitable option for me, all apps are real apps, you fucking faggot, i dont need to do ultra specific and obscure shit all the time, i need results and C give me that

>>106168080
no you just made a convoluted joke
as retribution i will now make your eyes bleed

What is it about C that makes people seethe so much?

>>106168057
Truly cnile

>>106167965
>Truly rust is a language for the white man.
You would be banned from every rust community if you wrote that with your real name.

>>106168342
perception of the language
its presented as something hard so midwits feel the need to do c to prove themselves
as opposed to use it as a tool, which has specific usecases
inevitably they get burned
then they seek revenge

theres also the shills
crabs have a good reason to try to demean c because they want to replace it
same with sepplefags
as to why exactly they do that i guess theres as many different motivations as there are shills
unresolved conflicts from childhood, monetary gains, politcal agendas, the need to see the world burn...

>>106168342
Rust was part of the Obama-Biden era woke astroturf that used undesirables to remove the competent old guard from all positions of authority and influence. It was possibly part of the final act of the "long march through the institutions".

c/c++ are part of the "Four Olds" that have to be torn down so we can all live in a utopia.

>>106168400
48 M paths sorted in 40 seconds without employing proper optimization techniques?
senile?

if anything its the equivalent of waking up with a raging erection

The problem with C/C++ isn't memory safety, it's the "header files, linking, cmake" circus you have to go through. It's the eco system that's the problem. Lack of memory safety can be seen as a feature in some cases, not a negative.

Memory safety (e.g Rust) has its place and I can see the appeal in a lot of use cases, but there are also many cases where the programmer KNOWS what they need to do and doesn't need a compiler to tell them they're not allowed

>>106168423
My name is Graydon Hoare. Rust is for the white man.

>>106168461
>header files, linking, cmake" circus you have to go through.
if this confuses you
you probably shouldnt be doing programming
especially not in C

>>106168484
write that in a gist in your github account

C-huds BTFO. C lang sucks.

>>106168495
>you're not a real programmer if you don't engage in our obtuse ritual
and people say Java devs are cargo cultists

>>106168342
outdated design

>>106168555
theres nothing obtuse about all that
headers are retardedly simple
you include text. thats it
its hard to imagine how that could be obtuse or confusing
and given that you can work with compiled libraries headers are also a self documentation mechanizm

linking. another retardedly simple concept
its just putting your program together from multiple sources

cmake. i never used cmake
i was gonna post my habitual makefile but have a makefile where i use sdl so that you dont screech that the project was too simple
NAME := gaym.7

CC := gcc
CFLAGS := -O3 -march=native -funroll-all-loops -pipe -fgnu89-inline -g
# CFLAGS_BUILD := -O3 -march=native -funroll-all-loops -pipe -Wall -Werror -Wextra -fgnu89-inline

SDLFLAGS := -lSDL2 -lSDL2_mixer -lSDL2_image -lSDL2_ttf -lm -lGL -lGLEW

SOURCE_DIR := src/
INCLUDE_DIR := inc/
CURRENT_PATH := $(PWD)

SOURCES := $(shell find . -name '*.c')
INCLUDES := $(foreach path, $(sort $(dir $(shell find $(CURRENT_PATH) -name *.h))), -I $(path))

all :
clear
$(CC) $(CFLAGS) $(SOURCES) $(SDLFLAGS) -o $(NAME) $(INCLUDES)

debug :
clear
@echo "=compiling debug version="
@echo
$(CC) $(CFLAGS) $(SOURCES) $(SDLFLAGS) -o $(NAME) $(INCLUDES) -DSHOW_RENDERING=1

this shit is at the same level as a docker-compose file

if you cant deal with what has been outlined above
you probably shouldnt be working with programming

>>106168625
>Comparing it to docker compose like it's a good thing
There's a lot of things to defend about C/C++, but your example isn't one of them. I like them, but it heavily suffers from the "N-no! The added work and verbosity k-keeps out retards!" mentality that is going to be the death of them as they continue to fall in popularity. It isn't a question of sufficient IQ to write a header file and linking, it's a question of "why are we still dealing with header files and linking in the current year?" Too many autists think that even an inch of movement to modernity may as well make it react web dev tier. C++ modules are a thing but even those are still a mess.

>>106168454
what are the other 3?

>>106169052
The "Four Olds" were specifically:
Old Ideas:
This included traditional Chinese philosophies, Confucianism, and any thought deemed to be bourgeois or counter-revolutionary.

Old Culture:
This encompassed traditional art, literature, music, and any other cultural expressions not aligned with communist ideology.

Old Customs:
This included traditional rituals, social norms, and family structures that were deemed to be outdated or feudalistic.

Old Habits:
This covered a wide range of behaviors, including religious practices, traditional forms of entertainment, and anything else that was not deemed modern or socialist.

The Red Guards, encouraged by Mao Zedong, actively sought to destroy these "Four Olds" during the Cultural Revolution.This led to widespread destruction of historical sites, cultural artifacts, and religious institutions, as well as attacks on individuals associated with traditional practices or beliefs.

>>106169102
yeah I googled it and already past the phase of embarrassment
thanks though

>>106169128
I actually thought you were just breaking my balls. It's all good bro.

>>106169033
>"N-no! The added work and verbosity k-keeps out retards!" mentality
>that is going to be the death of them as they continue to fall in popularity.

c doesnt need to be popular
and i dont give a shit to make it so
c is supposed to suit certain usecases
which it does. making it popular is bloat
which is more code to debug for the compiler people
and more ways to write the exact same which decreases maintainability

>why are we still dealing with header files and linking in the current year?
already told you
its a self documenting mechanism
and the c community is not gonna cater to zoomershits bc... its should look more like java!

you dont like c
youre not made for c
ok
stay away
simple as fucking ass. use sepples or rust or whatever
>but i wanna c
fuck off nigger were full

>>106169033
>>106169241
also
>why linking
because portability, you retard
youre talking out of your ass

>bc portability
and size
and versioning/upgrades
theres multiple reason why you want your software to be modular

you dont even know the basics but you have opinions
what the fuck is wrong with the new generations?

>>106169241
>>106169255
>>106169287
>Has autistic meltdown over 3 sequential replies as soon as his objectively archaic paradigm is challenged
Top kek, a tale as old as time. Do you have a "Popularity is bloat!" sticker on your ThinkPad?

>>106169311
>talks about me
very flattering
but youre digressing because you have fuck all to say about c besides "but i dont like headers!!!"

>>106167936
>generates substantially less assembly
Use case for minimizing assembly size? I rather have shit be fast

>>106169645
C++ is bloat is not fast. Especially in the above example where the C code goes directly to the raw APIs, whilst the c++ garbage goes through a heavy abstraction.

>>106169705
>heavy abstractions
I'd be surprised if it's more than a single function call of overhead

>>106169705
and yet all C compilers are written in C++. curious

>>106167807 (OP)
Opinion discarded.

>>106167990
>"Memory safety" is a meme that appeared inorganically 3-4 years ago
lmao, clueless LARPing zoomer moment