20 Jan
2014
20 Jan
'14
8:53 a.m.
On 19 Jan 2014, at 22:58, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
This is gorgeous.
The Moose distribution of Pharo looks like to be better suitable for code development
than the vanilla one. This makes me remember the Development image of Damien.
Do you really ***understand*** the implications?
Because once people will start to put dependencies everytwhere on roassal and start to run
smalllint on your code and ….
that you will have to follow it and merge and ….
you will look at the problem.
Without unload process that is systematically exercised, tools to manage dependencies and
a process to build and support modular images we will end up with a monolithic system.
I just tried to unload ProfStef and it was full of left instance behind. I tried to unload
Nautilus for example and RB.
Stef
Alexandre
On Jan 18, 2014, at 8:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
The GTInspector just became a performance analysis tool, too. You can simply inspect a
MessageTally and you get several useful views that help you identify performance
problems.
You can read a more detailed description here:
http://www.humane-assessment.com/blog/assessing-pharo-performance-with-gtin…
As an appetizer, I attached a screenshot with a Graph-ET chart (thank you Daniel Aviv for
developing this engine).
<MessageTally-chart.png>
To play with the code, you can just work in the latest Moose 5.0 image:
https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…
Please let me know what you think.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.