>program size is under 10MB
>performance not an issue
>uses a compiled language and not an interpreter
when will these old farts die off /g/?
>>52388808
A S S E M B L Y
S
S
E
M
B
L
Y
>>52388808
pl0x explain
>>52388808
Hopefully never.
>>52388808
>Learnt a new thing at college
>Has one use case where it's a bit better
>Shitposts on /g/
when will these ops die off /g/?
>>52388808
desu its more of a habit than anything serious
>>52388912
I don't understand
>>52388808
>Program is complex, requires performance
>Uses javascript/python
when will these people be gased /g/?
>>52388975
> gased
now that's to hard, don't you think!?
Just use the right tool for the right job!
>>52388808
>>52388808
Red and green triangles don't have the same angle, the white block exists from the gap
>>52388808
From the dip in image A's hypotenuse.
Simple optical illusion.
>>52389138
>>52389076
The graph paper says otherwise
>>52388808
>performance not an issue
This is literally never the case. Sometimes it is less of an issue than normal, but there is NEVER a time when slow is as good as fast.
>>52388808
Serious question: are you retarded?
>>52388808
>size of program determining whether or not performance should be an issue or not
fuck off retard
>>52389158
Bullshit. The graph paper is how I noticed it's different.
Red goes up three and over eight. That gives it a slope of 3/8.
Green goes up two and over five. That gives it a slope of 2/5.
2/5 = 16/40 > 15/40 = 3/8
>>52389158
Get a ruler
>>52389158
slope of green one: 5/2
slope of red one: 8/3
good meme retard
>>52389230
That's backwards. You gave the reciprocal of slope. Slope is rise/run and you gave run/rise.
atheists: 1
>>52389256
what's the point of that?
It's clear? now?
>>52389158
The adjacent leg of the green triangle is 2.5 times the opposite. 2.67 on the red one. This creates more space when you put the green one in front.
>>52389256
>this is autism
>>52388912
>Learnt a new thing at college
> implying
>>52389353
You're either one of those people who think they know everything, or you went to a really shitty college.
>>52389372
If you read through the books It's annoying how slow the courses are, even if they already showed to be able to teach more efficient plus faster
>not writing your antivirus in fucking node.js
https://code.google.com/p/google-security-research/issues/detail?id=693
>>52389438
It's not like the people learning are to slow
>>52389454
Holy shit. Am I misreading this, or was it actually as bad as it sounds? What else could the exploit do other than the shown example (opening calc.exe)?
The solution
>>52389622
it could run any exe on the users machine in the same context as the trend micro software. also it could be used to enumerate the users saved passwords in the trend micro password manager and send them to a remote server totally transparently. in short it is a major fuck up.
>>52389715
>The solution
I think you've just doubled the problem rather than providing the solution
>>52389168
>there is NEVER a time when slow is as good as fast
Yes there is. It happens when hardware is fast and cheap enough at the required scale that the required extra programmer time would be more expensive. Companies misapply this principle all the time, of course.
>>52389438
>If you read through the books It's annoying how slow the courses are
What does reading the book have to do with the rate the course is taught at? Also, what makes you think people want to read ahead for 4 or more classes?
>even if they already showed to be able to teach more efficient plus faster
Oh, you're retarded. My deepest condolences to whomever has to take care of you
>>52391309
Soon as this world crumbles, it will be an issue.
Power and carbon print will become extremely expensive and human slaves will get extremely cheap, so it will matter, even for minimal web server applications.
>>52390774
Why? It shows where the gap comes from, the top pieces are angled
>>52389249
i can dream in code ya know ?
>>52388808
but then that program has huge RAM usage
RAM usage > program size
