On Wed, 30 Dec 2009, Schwab,Wilhelm K wrote:

> Levente,
>
> I have to call you out on something: SSL is **definitely** not crap, and we 
> should have a clean interface to it, probably via OpenSSL.  I will eventually 
> create same if not beaten to it.

That's true, I was thinking about the rpc stuff.

>
> CORBA is also not crap.  To be blunt, none of the listed technologies are 
> crap if one has an externally defined problem (aka something that pay$ the 
> bill$) that requires communicating with something that uses them.  I will 
> grant you that most of them have a pretty high crap coefficient, and I would 
> not go out of my way to use them unless "forced" to do so.
>

Crap may not be the best word (but fits really well IMO), 
so overcomplicated bloatware.


Levente

> Bill
>
>
>
>
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Levente 
> Uzonyi
> Sent: Wednesday, December 30, 2009 5:45 PM
> To: [email protected]
> Subject: Re: [Pharo-project] Developer guide ... ?
>
> On Wed, 30 Dec 2009, Guido Stepken wrote:
>
> [snip]
>
> As others pointed out, these are implemented with blocks. What would you do 
> if, say you wanted to know how to do threading in java? Reading a book or 
> googling is helpful:
> - http://www.google.com/search?q=squeak+threads
> (I guess a chapter on processes would be useful in PBE/SBE.)
>
>> 5. Standards: XML-RPC, SOAP, RMI, CORBA, .... encryption (SSL) ...
>> Without having a precise idea, where to find working examples to
>> exchance data with other systems, i would hesitate to begin to do projects 
>> with Pharo/Squeak...
>
> Some of this crap is available at squeaksource/squeakmap.
>
> Levente
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to