Re:Learning Smalltalk from “Pharo by Example”
by echoless on Tuesday February 10, 2015 @01:41AM
(#9025720)
Isn't that a big setback for adoption though? The world is moving to multiple-cores, albeit slowly.
Re:Learning Smalltalk from “Pharo by Example”
by needusername on Tuesday February 10, 2015 @02:33AM
(#9025845)
It's hard to tell. If you compare yourself with traditional scripting languages like CRuby, CPython, JavaScript, Perl, PHP, Lua, … — they all use green threads as well. If you compare yourself to C++, C#, Java then things look differently.
It's probably a bigger issue for the commercial Smalltalk vendors. I would assume for a free, open source project this can be "forgiven" more easily.
Re:Learning Smalltalk from “Pharo by Example”
by dragonwriter on Tuesday February 10, 2015 @02:51AM
(#9025888)
> It's hard to tell. If you compare yourself with traditional scripting languages like CRuby, CPython, JavaScript, Perl, PHP, Lua, … — they all use green threads as well.
"CRuby" (MRI) since 1.9 and "CPython" (forever, as far as I know) use native threads with a global runtime lock so only one thread running Ruby/Python code (but possibly more running native code in the same process) runs at any given time.
AFAIK, most JS environments don't provide threads (green or otherwise).
That is correct. My understanding is that supporting multiple hardware threads would require major work in the VM and the development of a memory model. There's some quite critical code in there relies on certain things not being a point for a possible context switch.