Nathan Meyers wrote: > But I'm always curious about "wacky people" who like to > use thousands of threads (or tons of memory or zillions of levels of > recursion, etc.). Is that approach fundamental to solving the problem > efficiently, or do you use it because it's convenient and/or cool? > Sometimes the model involved is recursive/concurrent by definition, and a recursive/concurrent implementation is the cleanest way to implement it. What are we supposed to do in such cases? Perplex the situation badly in order to avoid using lots of threads? There are cases you simply can't do so. Dimitris
- Re: Green/Native threads David Wall
- Re: Green/Native threads Nathan Meyers
- Re: Green/Native threads Nelson Minar
- Re: Green/Native threads ptoscano
- Re: Green/Native threads Dimitris Vyzovitis
- Re: Green/Native threads Nathan Meyers
- Re: Green/Native threads Nelson Minar
- Re: Green/Native threads Dimitris Vyzovitis
- Re: Green/Native threads Juergen Kreileder
- Re: Green/Native threads Dimitris Vyzovitis
- Re: Green/Native threads Dimitris Vyzovitis
- RE: Green/Native threads Miles Sabin
- Re: Green/Native threads Nelson Minar
- Re: Green/Native threads Paul Ho
- Re: Green/Native threads Nathan Meyers
- Re: Green/Native threads Nathan Meyers