How many subsystems that do pretty much the same thing exist in Java?
 Or Programmable Hyperlinked Pasta?  
Try this:  do a set of Moose queries on a largish Pharo subsystem, say
GLORP, then do the same on EclipseLink, Toplink or Hibernate, either
with or without the JPA interfaces.  
Even with the tools in Moose the Java frameworks make little to no
sense compared to GLORP.  Neither do the names mean much other than
Hibernate, which itself could be taken n different ways.  
And JavaScript, well, what can you say about a language with prototypes
but no types to proto?
Most enterprise software is proof positive the Pastafarians are right -
I've seen plenty of flying spaghetti monsters.
AndrewOn Sat, 2018-04-14 at 00:31 +1200, Richard O'Keefe wrote:
> I was not talking about additional subsystems *for* Pharo,
> but subsystems already *in* Pharo.  For example, when I
> hover the mouse over "Epicea" in the leftmost browser
> panel, there is a pop-up that explains what is otherwise
> a rather opaque word.  But when I hover the mouse over
> "Fuel", nothing happens.  "Grease" => pop-up, "Growl", no.
> Actually there are three possibilities.  The third is that
> there's no pop-up but if you click, there is a package
> comment.
> 
> 
> On 14 April 2018 at 00:18, Peter Uhnák <i.uh...@gmail.com> wrote:
> > On Fri, Apr 13, 2018 at 2:05 PM, Richard O'Keefe <rao...@gmail.com>
> > wrote:
> > > There are a lot of subsystems in Pharo, and being a bear of
> > > very little brain, I have a hard time relating Zinc, Calypso,
> > > &c &c to, well, whatever they are.  I presume there is
> > > somewhere a list of topic/name/PFX triples for guidance.
> > > Can some kind soul tell me where it is?
> > > 
> > Until we have mature package manager (similar to Cargo or npm), you
> > have to use google.
> > On the bright side, with the move to git(hub), people are much more
> > likely to actually describe what their project does, and maybe even
> > a bit of documentation. This was almost non-existent with
> > SmalltalkHub.
> > 
> > Peter
> > 

Reply via email to