Pharo in the Browser with WebAssembly

I still remember the Byte issue on Smalltalk from 1981 [0]. To high school me it was The Future for sure. It looked <i>so cool</i>. I had no way to try it on the family Apple II+ [1] though.<p>Trying out various Smalltalk-family systems in recent years showed the advantages of implementing the entire system in one language and running it in one image. There&#x27;s a refreshing coherence and predictability to everything, and pervasive simplicity instead of fractal complexity.<p>You can browse the entire codebase in a single window - language&#x2F;compiler, math operations (except for the base primitives I believe), data structures, graphics, window system, all nicely organized. Methods, even critical ones, are mostly small, straightforward, and cruft-free. Many are just a line or two.<p>Smalltalk gives the developer immense power. You work directly &quot;in the code&quot;; your changes are live instantly. You can trivially modify the system itself - just go there and start typing. All in the same browser window. You can easily look inside any running program, change its data and even its code, and just keep going. Even now it feels futuristic.<p>You get powerful graphics and a window system out of the box instead of the usual story where you select OpenGL&#x2F;Vulkan&#x2F;GUI&#x2F;DOM libraries and configure tools like make&#x2F;rpm&#x2F;docker&#x2F;pip&#x2F;npm. That&#x27;s probably the most &quot;science fiction-y&quot; aspect by far.<p>In short, this was the &quot;Jetsons&quot; future that seemed possible back when I was getting started. The future we actually got, of course, is far less elegant and unified, and far more messy and practical. That&#x27;s probably for the best. But I still love Smalltalk.<p>[0] <a href="https:&#x2F;&#x2F;archive.org&#x2F;details&#x2F;byte-magazine-1981-08" rel="nofollow">https:&#x2F;&#x2F;archive.org&#x2F;details&#x2F;byte-magazine-1981-08</a><p>[1] <a href="https:&#x2F;&#x2F;archive.org&#x2F;details&#x2F;byte-magazine-1985-05&#x2F;page&#x2F;155" rel="nofollow">https:&#x2F;&#x2F;archive.org&#x2F;details&#x2F;byte-magazine-1985-05&#x2F;page&#x2F;155</a> (At the time I was sad because we didn&#x27;t have the extra memory it needed. Now I&#x27;m more impressed that it was even possible.)

Can&#x27;t believe what I&#x27;m seeing with my own eyes that Pharo is this fast, on a browser, on a mobile. I mean I get it that things have advanced and so much more insane things are out there (like running OS X Tiger with Infinite Mac, or SketchUp web, or...) but this still shocks me. Tech is advancing too fast for my monkey brain to pace with.

I played around with Pharo some time in 2017 or 2018, making a Minesweeper clone in it.<p>I really _really_ like environments where rapid and immediate iteration is possible, especially for any project with any artistry or exploration in its construction. One thing is that (in some cases) you see intermediate, emergent, or unintended results you&#x27;d not have seen otherwise.<p>Although not a particularly interesting unintended result, a logic problem (iirc) had the Minesweeper expand happen with each action (i.e. propagating cleared cells with each step rather than in an instant).

Nice!<p>So I assume this is the byte code interpreter compiled with Emscriptem? Didn’t Squeak have a similar try it out page?<p>I would assume there’s no attempt at Jitting or pre-compiling some of the image code, which would be a feat given Smalltalk dynamic nature and webassembly limited execution model.<p>I was hopping to have something like this to play with. How can you build the code?

I&#x27;ve never used Pharo before, but in my firefox it renders up and to the left too much. I&#x27;m not sure how the mouse is translated to the canvas but it seems like there is an issue with it (or vice versa and it&#x27;s the weird canvas scaling). Removing `transform: scale(calc(1 &#x2F; var(--world-dpr, 1)));` from the canvas css seems to fix it for me though.

I was hoping it was the 1999 video game alas

How come it is much snappier and uses less CPU than the same native version? I honestly don&#x27;t understand how this is possible.

Neat concept for playing with Pharo...but doesn&#x27;t having it in the browser kinda defeat the purpose?

I wandered about this a while ago, when VSCode went into Web. Later, after realizing how much download had to take place to have a remote OS ran, again the experience is very hacky with current hardware to software friction. It needs lots of drivers and resources to align experience with an actual OS.

It seems to break when zooming in&#x2F;out on Firefox (Linux). Zooming in reduces the size of the viewport and makes clicking the mouse happen somewhere else.

This webapp seems to break the back button on Android.

This title reads like Tamarian dialogue lol

Hijacked my back button on Android&#x2F;FireFox...

Obviously this post has been boosted quickly and mysteriously in 16 mins and it feels quite premature and it doesn&#x27;t even look remarkable at all.<p>Use with caution.