[Pharo-dev] Roadmap for Pharo 8.0

Norbert Hartl norbert at hartl.name
Fri Feb 8 10:57:31 EST 2019

> Am 08.02.2019 um 16:47 schrieb Serge Stinckwich <serge.stinckwich at gmail.com>:
> On Fri, Feb 8, 2019 at 4:41 PM Alexandre Bergel via Pharo-dev <pharo-dev at lists.pharo.org <mailto:pharo-dev at lists.pharo.org>> wrote:
> Dear All,
> At the consortium meeting we discussed the possibility to have a mini-Roassal included in Pharo8. Many opportunities exist: displaying graph of commits in iceberg, displaying UML within the code browser, visualizing dependencies between packages.
> We are motivated about it, and we should produce a runnable proposal ready to be evaluated by the community within a couple of months. 
> Does it make sense? Any thought about it? Do you have a wishlist?
> I will not be be strongly against it because I see benefits, but IHMO we need to reduce the size of Pharo image.
> Might be interesting to have charts included in the base.
> A+
I don’t agree. Why should we reduce the size of the default image? It should show a lot of things you can do with pharo. As everything is loaded from bootstrap we can have now every size of the image we want. I would rather see an official minimal image that people will download for building their software. But the development should contain everything that eases development and shows what pharo can do.
The critical border to me is what we provide in documentation. On the one hand we could benefit from powerful code documentation. But this could conflict with the minimum image we provide where people work on and these tools would be missing.


> -- 
> Serge Stinckwich
> Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO)
> Sorbonne University (SU)
> French National Research Institute for Sustainable Development (IRD)
> University of Yaoundé I, Cameroun
> "Programs must be written for people to read, and only incidentally for machines to execute."
> https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190208/96d6a2df/attachment.html>

More information about the Pharo-dev mailing list