Why do guys have to make tech so difficult? I just things to work.

File: cutecoder.jpg (94KB, 580x427px) Image search: [Google]

94KB, 580x427px

>>59229781
Sorry for the spelling ^-^

How do you edit a post on here?

File: 709vlB1.jpg (157KB, 1002x2048px) Image search: [Google]

157KB, 1002x2048px

>>59229781
at least this one is legible

File: 1410593854152.jpg (157KB, 600x520px) Image search: [Google]

157KB, 600x520px

>>59229806
>>59229781
I haven't taken programming since junior year
But even I can tell this is fucking bad code on both sides and is probably a false flag operation

>>59230039
The code on the left is from quake, used for calculating approximate inverse square roots very quickly. In the original source, most of the lines are commented.

>>59230039
Why did she removed the 'what the fuck' comment on the left code ?

>>59229781
>>59229806
women were a mistake

>>59230039

>bad code on both sides
Code on the right is incorrect (returns 5 for all cases of a == b)
Code on the left has had scientific papers written about it.

https://sites.math.washington.edu/~morrow/336_12/papers/ben.pdf

s-so can that code really steal nudes?

>>59231003

>Code on the left has had scientific papers written about it.

because its not actually clear what the code is for .. thus Karlie Kloss had a fucking point. The code is so unreadable you need a scientific paper to understand it.

When girls code they add cute comments and its crystel clear what everything does ^_^

>>59229781
Left: elder programming black magic tier
Right: elementary school computer club tier

>>59231108
I know you're being a faggot but if you look at quakes source you'll see that it is heavily commented.

>>59231108

>because its not actually clear what the code is for
It's not the code (implementation) that is not clear per se, but the algorithm itself. Most people don't understand how floating point shit works, and it would be silly to fully document how/why the function works in comments. At best, I'd say it could use a little cleaning up and modernization. For instance:

/* Fast implementation of inverse square root using Newton's method */
float Q_rsqrt(float number)
{
    union { int32_t i; float f; } res = { .f = number };
    float half = number * 0.5F;

    res.i = 0x5F3759DF - (res.i >> 1);
    return res.f * (1.5F - (half * res.f * res.f));
}

File: 1477085200020.gif (101KB, 500x513px) Image search: [Google]

101KB, 500x513px

>>59230381
>>59231003
Didn't know where it came from, since I hate this fucking meme

>>59231387
>Been so long that this just looks like moon runes to you
Damn, I know it's essentially just math, but still.

>>59229806
>>59229781
How do you know the left one was written by a man?

making fun of karlie kloss is like that fat bully who only picks on the smallest kid in school

have you no life?

>>59230039
>>59230442
jesus, it's obviously fake

this is the real tweet:
https://twitter.com/karliekloss/status/697837478141632512

note the post datetime and emoji used

learn to google

>>59231595
>https://twitter.com/karliekloss/status/697837478141632512
That links directly to cancer

>>59229806
it's fake btw

>>59231511

>Been so long that this just looks like moon runes to you
It's just C...

res is a union type, so its members share the same location in memory, or if applicable, the same register. This is preferable to casting around pointers, since this type of type punning is well-defined behavior in C11. I name the members i (for integer) and f (for float).

Everything else is just mathematical logic that is explained in the paper.