Thanks for this information, Ben. I have my protocol stack using sockets
constituted. I would then work on building a distributed registry and
package manager and take a close look at distributed logging.
> On Tue, Dec 29, 2015 at 6:05 AM, Robert Withers
> <
[hidden email]> wrote:
>>
>> On 12/28/2015 01:42 PM, Marcus Denker wrote:
>>>> On 28 Dec 2015, at 19:33, Robert Withers <
[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> On 12/28/2015 01:18 PM, Sven Van Caekenberghe wrote:
>>>>>> On 28 Dec 2015, at 19:11, Robert Withers <
[hidden email]>
>>>>>> wrote:
>>>>>>
>>>>>> I got you, stephano. I do not wish to be banned.
>>>>>>
>>>>>> Leaving aside established spiritual traditions, but picking out the
>>>>>> pattern for exploration, what would you say the meta-meme of Pharo is? In
>>>>>> other words, what is the mission statement? This would help me grasp the
>>>>>> motivations of the community and is not a meaningless exercise for the
>>>>>> community, from a leadership development perspective..
>>>>>
http://pharo.org/about.
>>>>>
https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf>>>> This is awesome, thank you for posting it. It mentions a roadmap. Is
>>>> there such a page?
>>> We are working on an updated roadmap.
>>
>> Thanks for setting the right expectations, please enjoy the holidays. I will
>> enjoy it when it is properly aged.
>>
>>> We will update it to form a roadmap soon… (I wanted to have it done
>>> already, but was busy
>>> with other things end of the year…)
>>
>> I understand and the results of your efforts are plain to see. Pharo-5 runs
>> my work well. I have been reading your section 4 in the Vision document with
>> great interest. Particularly, I find I like 4.2, 4.3, 4.5, 4.6, 4.7, 4.8,
>> 4.11 and 4.12. I would like to try my work on top of ocean.
> 4.2 FileSystem was integrated integrated into Pharo 2
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=filesystem>
> 4.3 Announcement were introduced in Pharo 1.3
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=announcements>
> Ephemeron VM support available soon in Spur VM (?). Probably work
> more needed image side (?)
>
> 4.5 Bootstrap Core - Work In Progress
>
https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-3-Minimal/Full>
> 4.6 Fully parametrized compiler tool chain
> I'm not clear on what "fully parameterized" encompasses, but the old
> Compiler was replaced by new OpalCompiler in Pharo 3 - I guess to
> satisfy this.
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=opal>
> 4.7 Packages as real objects
> Begun in Pharo 2 with introduction of RPackage. Completed in Pharo 4
> with removal of PackageInfo.
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=package>
> 4.8 Package Meta-Data
> Not sure what this entails or status. Package Manifest introduced in Pharo 2
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=manifest>
> 4.11 New Network Layer - I don't know.
>
> 4.12 Serializers - Fuel is the default serializer since Pharo 2. I
> don't know the rest of the scope for this point.
>
https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=fuel&type=Code>
> cheers -ben
>
. .. ... ^,^