You're right of course; I made bad choice of words. It is challenging me
to explain what I meant as there is something reasonable I am trying to
say. I will try.
We all have our own interests and projects we wish to achieve in Pharo.
Often this means everyone is working on their own directions and
interests and often this means working alone without a team-oriented
project. People with similar interests will join efforts and plans.
Other projects have been determined to align with pharo's core vision
and BigTalk and discussion has yielded plans and work proceedeth
collaboratively.
I work on SecureSession and CryptOCaps as my own interests and I get
much welcome help but they are my projects. I tr to talk about them in
hopes others will use them, but it is my efforts which pay off.
SecureSession is solid and usable.
The realm of BigData is different. I have knowledge and experience there
and I think it would be powerful for Pharo, but they aree not my main
focus. If Pharo wishes to get into this space, it best be done
collaboratively which requires some BigWords to coordinate. As they are
not my main focus and needs collaboration, a team should form around it,
whether it is in the PharoVision or not. This is where I think I
misspoke, making it official.
I wish I had twice the time available, to work CryptOCaps and BigData,
but I do not. If nobody is interested in seeing how Pharo does with
BigData there is not anything I can do nor could I offer my experienmces
there to assist. My suggestions to form a BigData team around it, to
coordinate and collaborate, fall short if there is no interest. I will
stop encouraging this and refocus back on my work.
My apologies for the distractions,
Robert
On 12/29/2015 07:20 AM, Dimitris Chloupis wrote:
Should be ? There is no "should be" it is what it is, if anyone wants
something more he is more than welcomed to stop writing to the mailing
list and use that time instead to sit his ass down and make the code .
The potential of Pharo is unlimited but taking advantage of it is hard
work and nothing else. BigData frameworks dont come from BigWords.
I wanted Pharo to work with python and use python libraries . Did I
came to this mailing list to write that pharo "should be" able to use
python libraries, because python is super popular and its constantly
growing ?
Nope !
I sat down my ass and worked hard to make it happen and I did
accomplish it. Still much to improve but there is no substitute to
hard work and putting the time to improve pharo.
You wanna use Jars from Pharo , no problemo, work hard and do it. But
please dont tell me what should be in the vision of Pharo, why BigData
and not 3d graphics, why 3d graphics and not network libraries, why
network libraries and not more IDE tools, why IDE tools and not more
advanced language features, why advance language features and not a C
API , why C API and not web development frameworks ?
In the end nothing , NOTHING , should be outside the scope of a
language that wants to call itself "turing complete" . No goal is
higher than something else. Each coders has different needs . What it
"Should be" is people that are willing to work hard to make THEIR OWN
NEEDS a reality using a tool THEY LOVE using. Its a choice.
And a Stef so well says it
Pharo is Yours
On Mon, Dec 28, 2015 at 9:44 PM Robert Withers
<[email protected] <mailto:[email protected]>> wrote:
What I mean is that an undertaking of this scope should be in the
Vision
and on the roadman for Pharo, with a broader concerted commitment to
enterprise BigData integration.
robert
On 12/28/2015 02:29 PM, Robert Withers wrote:
>
>
> On 12/28/2015 12:19 PM, Frank Shearar wrote:
>> On 27 December 2015 at 16:11, Robert Withers
>> <[email protected]
<mailto:[email protected]>> wrote:
>>> This would be awesome in Pharo:
>>>
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol.
>>>
>>> Since we cannot yet call JARs, implementing the wire protocol
and API
>>> proxies would really be huge from an enterprise pharo
standpoint. If
>>> other
>>> folks are interested in working on this, I could help out.
>> Having a Kafka client in Pharo would indeed be awesome. But who
cares
>> about calling JARs? It's a wire protocol; write a client
against that
>> and you're done.
>
> Yes, although I would still like to load JARs, but for different
> reasons. That aside, yes implementing the wire protocol would be
> really happening. I'll help. I don't want to own it. It would
> definitely be enterprise.
>
> robert
>
>
>>
>> frank
>>
>
--
Robert
. .. ... ^,^
--
Robert
. .. ... ^,^
