Let n = number of cores in your computer in
is it really fucking hard to split the tripcode domain into n equal parts and spawn n processes?
Name:
Anonymous2009-04-05 23:36
>>1 Is it really hard to write multi-threaded apps?
Yes. Neither Se nor Sepples has native support for threading, and if you are using anything else the speed loss from the excess bloat makes using threading redundant anyway.
>>8
Funny, I just checked the C89 and C99 standards, which define exactly what C should and shouldn't be able to do. Threading wasn't in there. Good luck porting your code off your 0.02% market share operating system.
>>10
Funny, I just checked the real world, and nobody has ever programmed in Standard C. They didn't give a fuck what's in there. Good luck finding an OS my pthread code isn't already ported to.
>>13
Funny, I use the real world on a daily basis and with regret must inform you that GNU/HURD ``programmers'' and linux kernel tweakers are not to be found in it. Because you are retarded I will paste straight from the "PThreads WIN32" page. Win32 does not, and is unlikely to ever, support pthreads natively.
I'm looking forward to your sincere apology.
Fucking threading. Tripcode explorers don't need a shared address space because the various instances don't need to communicate, and if you're using one process per core there's no additional overhead compared to threading once the processes have been created.
Using multiple processes instead of multiple threads also has the advantage that you can distribute it over several machines instead of just your shitty dualcore desktop.
Name:
Anonymous2009-04-06 11:39
>>26
Threading has the advantage that you don't end up trying the same combination multiple times, and if you precalculate the salt tables, you can save time and memory because it can then be shared among all threads.
Also, multiple threads and multiple processes are not mutually exclusive options.