News:

Pretty crazy that we're closer to 2030, than we are 2005. Where did the time go!

Main Menu

Developing Multithreaded Applications

Started by 01Linux, July 08, 2005, 02:15:30 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


rabbit

public class thing extends Thread
{
    public static void thing()
    {
        super("thing");
        // blarg
    }
}
Java has had multi-thread simplicity for a LONG TIME.

MyndFyre

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: Joe on January 23, 2011, 11:47:54 PM
I have a programming folder, and I have nothing of value there

Running with Code has a new home!

Quote from: Rule on May 26, 2009, 02:02:12 PMOur species really annoys me.

Tuberload

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
I am prepared to be ridiculed for what I believe, are you?

Warrior

One must ask oneself: "do I will trolling to become a universal law?" And then when one realizes "yes, I do will it to be such," one feels completely justified.
-- from Groundwork for the Metaphysics of Trolling

iago

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.