On Tue, Dec 29, 2015 at 11:20 PM, Dimitris Chloupis <[email protected]> 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.
I think Its okay to sometimes advocate for features. The *hope* of course is that the idea sparks the interest of others. It just needs to be moderated by: expectation, channel noise and own-effort (as you say). The word "should" is a loaded term with a subtle difference in two 1. used to indicate obligation, duty, or correctness, typically when criticizing someone's actions. 2. used to indicate what is probably [a good idea]. I often fall in the trap of meaning the second, but my wife hears the first --> trouble. cheers -ben > 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]> > 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]> 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 >> . .. ... ^,^ >> >> >
