Mark-Jason Dominus' rejection of Design patterns ( he was essentially quoting someone else ) is they do not represent an advance, but rather a manual implementation of something missing from the language. The earliest machine language had the Subroutine design pattern, implemented by saving certain values to certain places, and jumping to certain machine addresses; every language since simply has functions and/or subroutines. Java has an Interator design pattern; Perl has for() acting on a list.
In the same way, threads, forks, selects deal with implementation. People are searching for an abstraction which simplifies away the complications and allows a higher level of comprehension.
So far, they've had limited success. Maybe the problem needs several abstractions, for different situations. But you can't fault them for trying.
As Occam said: Entia non sunt multiplicanda praeter necessitatem.
In reply to Re: Your main event may be another's side-show.
by TomDLux
in thread Your main event may be another's side-show.
by BrowserUk
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |