I second trying Pharo under WSL for robustness. I wrote a blog entry on how to set it up, and I think it's still valid: https://fuhrmanator.github.io/2019/02/27/Pharo-in-WSL.html - Since you'd be using WSL2, you have to do things differently for the DISPLAY variable: https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333
As to the question of why Windows on Pharo is less stable, I have some experience using over the years other programs ported to Windows from OSS, e.g., LyX and InkScape. I have seen a repeating pattern: key OSS devs of certain libraries are hyper-sensitive to how things are done in Windows (rightly so, some things are very different and require creative solutions that break when Windows changes). We all know OSS resources are limited. Consequently the libraries don't get the love.or testing they need. Despite this I think the Pharo team does a great job supporting Windows. On Thu, 22 Apr 2021 at 15:39, Petter <petter.eges...@gmail.com> wrote: > It might be worth trying to run Pharo under wsl if you have to go Windows? > I > do on my job laptop and it works fine for me. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -- Christopher Fuhrman, P.Eng., PhD *Professeur au Département de génie logiciel et des technologies de l'informationÉTS (École de technologie supérieure)* http://profs.etsmtl.ca/cfuhrman +1 514 396 8638 *L'ÉTS est une constituante de l'Université du Québec*
