threading and multicores, pros and cons

[sjdevnull at yahoo.com]

On Feb 14, 1:44 am, Paul Rubin <http://phr...@NOSPAM.invalid> wrote:
> > When a customer comes with his new beautiful dual-core server and
> > get a basic plone install up and running, he will immediately
> > compare it to J2EE and wonder why he should pay a consultant to make
> > it work properly.  At this time, it 's not easy to explain him that
> > python is not flawed compared to Java, and that he will not regret
> > his choice in the future.  First impression may be decisive.
>
> That is true, parallelism is an area where Java is ahead of us.

Java's traditionally been ahead in one case, but well behind in
general.

Java has historically had no support at all for real multiple process
solutions (akin to fork() or ZwCreateProcess() with NULL
SectionHandle), which should make up the vast majority of parallel
programs (basically all of those except where you don't want memory
protection).

Has this changed in recent Java releases?  Is there a way to use
efficient copy-on-write multiprocess architectures?