If only the Pharo community knew that, they would have jumped to fix this issue! Because clearly they have all the time and resources in the world, and they only keep this issue open out of spite...

It's a volunteer non profit project. If people haven't done, clearly the don't have the time to do it over other things.

Tsk, tsk-ing them for not having fixed everybodys and anybodys pet peeves is beyond meaningless.

It's not like random non-Pharo using programmers are entitled to anything. Or like anybody forces them to use the platform.

If they don't like it, it's rather "don't let the door hit you on your way out".

If, otoh, they want to use Pharo they can. If they find that future important, they can help build it.

I hope you feel better after that little outburst. If this is your reaction to mild criticism of obvious shortcomings, it puts out quite a welcome mat.

I'm not the "Pharo community", just someone trying out Pharo.

But I don't think entitled criticism helps or is welcome in any community project.

It's easy to point at anything and ask them why they haven't done it yet, and that it's this "mindset" that keeps them small.

As if if they had a different mindset they'd also have magical resources.

It's the entitled ones who are the "arseholes", and project after project has commented publicly about how toxic they are for the actual community.

I'm just restating the obvious.

There were more pressing matters to solve. A lot of Pharo devs are using Macbook Pros with retina display, so they have an itch to scratch. But the issue lies on the VM side for now, so that limits the numbers of contributors + PharoVM reunited on the OpenSmalltalk initiative and that is no walk in the park.