I agree, it's also better to use a language from the current century that lets you get work done instead of micromanaging memory.
>>59103379
/thread
>>59103379
t. python brainlet
>>59103348
who casts the return of malloc in 2017?
Go back to >>>/ck/ you fuck.
>>59103420
you'd be surprised
>>59103379
POO
>>59103409
>>59103475
>t: tryhards
If you use C for anything but systems programming that take actual advantage of its features in 2017, you're trying too hard.
>>59103496
>it's a buttblasted codemonkey forks the C language then blames C when his code is exploited episode
>>59103420
sepples niggers
this 'stop x' varg meme is really fucking shit.
>>59103379
>current century
Off the top of my head I could only think Go and Trumpscript, mind giving non-bloated examples?
>>59103348
>write code that won't compile later under C++
Fuck off.
>>59103619
>C++
Fuck off.
Reminder to all good gentlemen to call your variables things like "class" and "public" where sensible, and implicitly cast where sensible.
>>59103348
Nords are the purest whites to exist.
>>59103582
The only bloated part of Go is the runtime it crams in every binary.
>>59103767
>hurr durr my C code shall never be used as part of a C++ project
KYS
>>59103825
>hurr durr I like poopoo
Ban sepples.
>>59103420
I do because I manage my own memory but write in C++
it's actually good that people force C is kill meme, we would have less retards in C community
>>59103348
>>59103420
What's wrong with casting the return of malloc?
>>59103887
Job security for us my dude
>>59103959
It's completely unnecessary unless you're using C++, and you shouldn't be using malloc in C++ anyway
the persistence of unsafe langauges like C is why software """engineering""" will never be considered real engineering
>>59103379
Moore's Law is pretty much done. Intel was stuck on 14nm so long that AMD caught up. The only way to make faster programs is to micro-optimize every machine instruction. Assembly is the language of the future.
>>59104149
Bridges can be unsafe if they aren't built right, should they be outlawed too?
>>59104167
real engineers (eg the people who make bridges in first world countries) take safety seriously
>>59103420
C++ programmers.
>>59104127
Holy shit it's actually optional.
Why does nobody tell me this stuff
>>59104127
>and you shouldn't be using C++ anyway
ftfy
>>59103517
>it's a code monkey who thinks he's not a code monkey because he spends more time worrying about looking cool and hip than actually writing working code
laughing my ass off at you're life
>>59104334
>this monkey thinks anything except C and ASM is `code`
>bet he can't even implement his own kernel
>>59104184
And real c engineers take memory safety seriously, it isn't their fault if some retard kid can't figure it out
>>59104387
if they were serious about it they wouldn't use a language that is inherently unsafe
>>59104410
C is perfectly safe
>>59103420
>who casts the return of malloc in 2017?
It's required in C++ to prevent a type-mismatch error.
>>59104410
It is safe though, not know how to use it properly is unsafe
>>59104150
Spoken like a true armchair developer who's likely never written more than a hello world-tier program in assembly.
The future lies in increasingly better compilers, better algorithms, better language, and maybe faster storage as well. Assembly is a terrible idea for any piece of modern software; even if you can somehow end up with a faster product than a good compiler will generate (you more than likely won't), you'll still have an impossible to maintain mess that over-complicates simple problems a higher level language will articulate easily, and also keep safer from mistakes..