Hi, In my opinion, Pharo provides the strongest infrastructure for understanding a system from all technologies I have seen. So, if you say that Pharo is a bit "under featured in, then I think we are not referring to the same thing :).
May I ask how you are using the inspector? For example: - do you extend the inspector? - do you construct visualizations about your system in the inspector? - do you write queries about code in the inspector? Cheers, Doru > On Jan 9, 2017, at 3:42 PM, Hilaire <hila...@drgeo.eu> wrote: > > I know this path of understanding code while it is running (inspector or > debugger), but it is still a tedious path, and I feel Pharo is a bit > under featured on that specific department, therefore my question on Moose. > > Hilaire > > > > Le 09/01/2017 à 15:09, Tudor Girba a écrit : >> That is why my advice is to not try too long to understand Pharo code >> statically because this is not where the power of Pharo is. You are in a >> much better position to understand a system when it’s running. So, the tools >> that I use the most are the inspector when I need to understand structural >> relationships or contracts between objects, and the debugger when I need to >> understand some algorithmic steps. Even when I look for code structure >> patterns, I mostly use the inspector because it allows me to query. Then you >> augment these tools with custom views and you get quite far. > > -- > Dr. Geo > http://drgeo.eu > > -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."