[squeak-dev] Re: [Pharo-users] evolutions of squeakelib & crypto (Reed Solomon)

Ben Coman btc at openinworld.com
Sun Dec 6 02:24:13 UTC 2015


On Fri, Dec 4, 2015 at 11:57 PM, Robert Withers
<robert.w.withers at gmail.com> wrote:
> Now I think you are right on with your observation. Additionally, the number
> of dialects could increase further with Fuel serialization, just port
> SecureSession and bits.
>
> Alright, I came up with a name and it may border on the egregious ...
> presenting ...
>
> "Maelstrom"

Great sounding name.  However some general advice for the community,
since I see a lot of great sounding project names drowned out in the
noise of our web-search-centric universe.  A litmus test for project
naming is using google search to find which return low search results.
Today, its more important to be unique than any other attribute of a
name.  So in general, *dictionary* english words are not the best.
One technique is to intentionally mispell the word you like.  Here are
some comparative examples (note, the surrounding quotes are required
to avoid google trying to be helpful and correct the spelling)...

"maelstrom"    --> 7,480,000
"maelstroom"  --> 6,200
"maelstrum"    --> 2,280
"maelstruum"  --> 7

Lots of interesting other techniques can be found by searching on:
techniques to generate brand names or domain names.

cheers -ben

>
> A new distributed metric will be established in Maelstrom to measure intra-
> & inter-vat activity: "Sanguinity".
>
> Robert
>
> PS. thanks for pointing out Fuel support for older squeaks.
>
>
> On 12/04/2015 10:25 AM, Sven Van Caekenberghe wrote:
>>
>> Another suggestion: if you intend to make something cross dialect and hope
>> to get traction, I would not use a project name which contains one dialect,
>> but something more general like Cryptography, or some cool project name,
>> like Seaside, Fuel, ...
>>
>>> On 04 Dec 2015, at 15:43, Robert Withers <robert.w.withers at gmail.com>
>>> wrote:
>>>
>>> I use squeak 5.0 and would want the Fuel support to customize for wire
>>> serializations and substitutions, such that Squeak and Pharo could talk to
>>> each other, and all other Fuel environments. The Fuel changes I made are in
>>> the Pharo port of SqueakElib in the SqueakElib-CapTP-Serialization category
>>> and consist of a Decoder, Materializer and a Materialization.
>>>
>>> Robert
>>>
>>> On 12/04/2015 09:35 AM, Esteban Lorenzano wrote:
>>>>
>>>> which squeak version?
>>>> of what?
>>>>
>>>>> On 04 Dec 2015, at 12:15, Robert Withers <robert.w.withers at gmail.com>
>>>>> wrote:
>>>>>
>>>>> I just realized that the squeak version uses ReferenceStream while the
>>>>> Pharo version uses Fuel, so the binary serializations are different and they
>>>>> won't speak to each other. Any chance that Fuel is ported to Squeak?
>>>>>
>>>>> Regards,
>>>>> Robert
>>>>>
>>>>> On 12/04/2015 06:11 AM, Robert Withers wrote:
>>>>>>
>>>>>> I am unable to import these files into SqueakSource, so it may be best
>>>>>> done from inside Pharo with Monticello. Here are working Crypto and
>>>>>> SqueakElib in Pharo, prior to SecureSession refactoring and Reed Solomon. I
>>>>>> include the correct version of LayeredProtocol.
>>>>>>
>>>>>> Regards,
>>>>>> Robert
>>>>>>
>>>>>>
>>>>>> On 12/04/2015 05:47 AM, Robert Withers wrote:
>>>>>>>
>>>>>>> Best Regards
>>>>>>>
>>>>>>> http://www.squeaksource.com/Cryptography.html
>>>>>>> http://www.squeaksource.com/squeakelib.html
>>>>>>>
>>>>>>>
>>>>>>> On 12/04/2015 05:44 AM, Robert Withers wrote:
>>>>>>>>
>>>>>>>> After my password reset on squeaksource, I committed to both
>>>>>>>> Cryptography and SqueakElib, project links below.
>>>>>>>>
>>>>>>>> In the case of Cryptography, I had a version ported to Pharo ... I
>>>>>>>> will organize Pharo ports of both after Reed Solomon is stable, and announce
>>>>>>>> them to the Pharo list. This way both environments can be supported through
>>>>>>>> this one repository.
>>>>>>>>
>>>>>>>> Robert
>>>>>>>>
>>>>>>>> On 12/04/2015 04:35 AM, Stephan Eggermont wrote:
>>>>>>>>>
>>>>>>>>> On 03-12-15 23:06, Robert Withers wrote:
>>>>>>>>>>
>>>>>>>>>> Are any of these used by both squeak and Pharo? That would be the
>>>>>>>>>> right
>>>>>>>>>> move I think. I will ask about getting my password reset for
>>>>>>>>>> squeaksource, since that is where the old code resides.
>>>>>>>>>
>>>>>>>>> All of them. Mostly timing of project start/high activity and who
>>>>>>>>> are
>>>>>>>>> maintaining it decided on platforms. There was a time when
>>>>>>>>> squeaksource was not so stable and then many projects migrated, and I
>>>>>>>>> currently hear least about stability issues from ss3, but the load on
>>>>>>>>> smalltalkhub is much higher, I assume, as that is used for the pharo ci.
>>>>>>>>>
>>>>>>>>> In the not so far future Pharo is likely to move to a git based
>>>>>>>>> infrastructure, using libgit2. Early adopters are already using it.
>>>>>>>>> I haven't heard the squeak ideas about that.
>>>>>>>>>
>>>>>>>>> Stephan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>
>
>


More information about the Squeak-dev mailing list