There was a thread about this two years ago.
��
It used to come standard in Squeak.�� When I knew it, it couldn't quite
handle HTML 3.2.�� I imagine it was removed from Squeak (and SqueakMap)
because it was quite impractical to keep up with the rapid changes in
the web.�� It would be cruel to say that some browser engineers never
saw a feature they didn't like; the truth often hurts.
There is already something called tODE, which apparently can make Pharo
tools visible in browser windows.�� That may be a better way to go.
ST/X went to the trouble of including its own Javascript and JVM
implementations, but of course JS changes quite rapidly too and is
no longer the little language it was when introduced.�� Heck, the
ECMAScript specification is bigger than the source code listing of
the mainframe operating system I used as an undergraduate.
We already have the tools needed to talk to WebKit; there is very
little benefit to the Pharo team from pouring vast resources into
duplicating what already exists.����