Neat article on MSDN, http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/multithreaded_netcf_apps.asp
public class thing extends Thread
{
public static void thing()
{
super("thing");
// blarg
}
}Java has had multi-thread simplicity for a LONG TIME.
Yeah, threading in .NET is a cinch.
Of course in Java, you have to have a stupid extra worker class to support multithreading. .NET supports function pointer (delegate) callbacks. :) Far superior, especially when you consider that they're type-safe at compile time.
Quote from: MyndFyrex86] link=topic=1836.msg17134#msg17134 date=1120835014]
Yeah, threading in .NET is a cinch.
Of course in Java, you have to have a stupid extra worker class to support multithreading. .NET supports function pointer (delegate) callbacks. :) Far superior, especially when you consider that they're type-safe at compile time.
Yes far superior if you're interested in running a bloated windows application only. :P
Amen Tuberload, Amen.
Incidentally, there is less overhead to spawning a child process on Linux (using fork()) than there is spawning a thread on Windows. I wish I had a source for that, but it's in a book I read a little while ago.
On Linux, a lot of things (particularly daemons) will fork when they get a request. The child process (which can share memory with its parent, in an efficient way) handles the request and the main process goes back to listening.