I completely agree with you. I have zero issues of main pharo developers kicking out libraries that are not so much used by pharo users. Those libraries are perfectly capable of existing as third party.

I also love the plan to make pharo modular, remove libraries from inside and make it easy to install. This way each one of us can easily make an image tailor made for his/her needs. Each pharo user is an individual with individual needs.

Installing libraries is dead easy with the Configuration Browser , including their dependencies , just one click away.

Of course that leaves whos going to maintain that stuff.  I agree with Marcus here, "you want it in pharo , code it".The theme support in Pharo is very powerful , I know because I created my own custom blue theme and a tool to allow easy customization of theme colors with zero coding (Nireas). I expected that by now Nireas would be replaced by another way more powerful theme manager but it has not. Why ? Not because my theme manager is very good, but because the community is just too small. I love using my blue theme and fits perfect to my taste and needs ;)

In the end no code can be more personal than the code you create.

There is no need for everything to exist inside the image , great things can exist outside too. All it needs people who really care about pharo by coding for it.