Thread replies: 7
Thread images: 2
Thread images: 2
File: 79e0f76f22f429dc6a79ebbe8f3b484d.jpg (20KB, 306x306px) Image search:
[Google]
20KB, 306x306px
Why do people do stupid shit like malloc 32 bytes?
There's no reason to malloc unless you're working with over 1mb buffer.
Also people using uint16_t when 16 bit register is slow as shit on 64 bit cpu, leaving unnecessary branches everywhere in their code, using too many unnecessary variables forcing the compiler to keep hitting the stack.
We have a whole generation of smug hipsters babby and their ruby/js. Every year hardware keeps getting faster and software keeps getting more bloated.
I don't understand why low-level programmers even created these type of languages. The software profession is riddled with mediocrity. It won't be long before we're seen as nothing more than cybercoolies.
>>
File: 1475891815679.jpg (682KB, 797x1182px) Image search:
[Google]
682KB, 797x1182px
>>58253234
You don't?
>>
>>58253261
Of course not. No sane person would use the heap for 32 bytes. You really shouldn't even use the stack if possible.
>>
The thing is they all think the performance impact of their bloated code is negligible, but it all adds up. You especially feel it on mobile os like Android where some apps written using NDK run smooth like butter while the rest of the phone UI is laggy as shit. And Google is trying to salvage the broken POS that is Java instead of putting more resource in their NDK, one reason Android will always be shit compared to iOS.
>>
>>58253234
>babby
baby
>>
>>58253435
newfag gtfo
>>
>>58253469
>newfag calling out newfags
Thread posts: 7
Thread images: 2
Thread images: 2