<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
<blockquote
cite="mid:1b61adf40807062209v3b18e2e6sa50ad24899cdecdb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Everything
you say, to the letter, can and has been said about manual memory
management. </blockquote>
</div>
</blockquote>
<br>
Not in my view.<br>
<br>
<br>
<blockquote
cite="mid:1b61adf40807062209v3b18e2e6sa50ad24899cdecdb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The
point you're apparently not getting is that the "one native thread per
image" is not only a workaround to avoid some very nasty issues down in
the VM, it also provides a clean *model* for concurrency. </blockquote>
</div>
</blockquote>
I do get that you guys think that.<br>
<br>
<br>
<blockquote
cite="mid:1b61adf40807062209v3b18e2e6sa50ad24899cdecdb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">No
such model exists for shared state concurrency which is the real
problem - since all synchronization is manual, it is pretty much
impossible to write large scalable systems correctly with manual locks
and mutexes. Just as it is impossible to write large scalable systems
correctly with manual memory management.<br>
</blockquote>
</div>
</blockquote>
<br>
No, it's not impossible as evidenced by many large systems written in
C++ and other languages without automatic garbage collection.<br>
<br>
Automatic synchronization is a hot field of research.<br>
<br>
<br>
<blockquote
cite="mid:1b61adf40807062209v3b18e2e6sa50ad24899cdecdb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"></blockquote>
<div><br>
<br>
It's not *that* hard to write a large, scalable, concurrent systems
using Processes and Semaphores. Sure, at times it can be difficult with
horrible bugs that take a decade to manifest, but if you use consistent
patterns and encapsulate complex behaviour well, it is quite tractable.<br>
</div>
</div>
</blockquote>
I concur.<br>
<br>
One of my points is that it's one thing to say we simply doing it this
one particular way and quite another to assert it can't be done when
there is a Smalltalk that has done it (Smalltalk MT).<br>
<br>
All the best,<br>
<br>
Peter<br>
<br>
</body>
</html>