Caffeine updated for Pharo 7
I’ve updated Caffeine to run Pharo 7; please try it out! There was one virtual machine bug (primitivePerformWithArguments wasn’t manipulating the stack correctly), and I had to turn off a few Pharo features (like libGit support, which uses LibC, something I haven’t faked in the virtual machine yet).
Many thanks to the Pharo hackers in the RMOD team at INRIA Lille, for hosting me at their sprint on Friday, 27 September 2019. It was great hanging out and coding with you all. We’ll get that Pharo Apple Watch screenshot soon. :)
thisContext 
29 September 2019 at 5:46 pm
I am curious about the difference in performance between running Caffeine in the debug tab, and as an ‘app’ in the web page. In the debug tab the performance is generally quite snappy – dragging windows etc. In the webpage, the updates are quite slow, and there is a lot of memory paging – just based upon the spinning thingy.
However, when I run
(1 to:1000) do: [:each| Transcript show: each;cr]
The performance difference goes the other way. The debug tab shows the numbers incrementing in the Transcript – as one would expect. The app shows the loop finishing almost immediately with the last few numbers printed to the Transcript.
Thoughts?
LikeLike
29 September 2019 at 6:31 pm
Hm, that’s really weird. :) I’ll see if I get the same thing. I recently made the object memory snapshot much smaller… you might want to clear the application cache (including the IndexedDB) for your web-page version, just to make sure you’re comparing the same bits in each.
LikeLike
29 September 2019 at 7:53 pm
I just tried this on three different browsers: Chrome, Safari and FF. The experience (of the web page based version) was the same on all three. I can do a screen capture video if that helps at all
LikeLike
29 September 2019 at 7:54 pm
Sure, that would be interesting.
LikeLike
29 September 2019 at 9:20 pm
OK, here is a brief video https://vimeo.com/363151462
LikeLike