I remember my 10 year self struggling learning to code basic back in 1988
on an Amstrad CPC 6128 with Locomotive Basic that required entering line
numbers before the code statement. IDEs , code editors and what else were
unheard of for me at least and even if they did exist would be nowhere near
th
On Thu, Aug 17, 2017 at 4:25 PM Esteban Lorenzano
wrote:
> hi Dimitris (good to see you around ;) ),
>
>
Not going anywhere , just taking a break from Pharo :)
> thing is… we want to improve our tools.
>
> great
> And improve tools sometime means to add stuff (I’m not very happy with it
> eit
Got an architecture discussion with a client this morning and a lot of pain
they face is that there are too many choices out there on some platforms.
A batteries included distro with one good framework doing its thing nicely
if really a good thing to have.
It reduces the amount of choice and thus
> On 17 Aug 2017, at 15:24, Esteban Lorenzano wrote:
>
> hi Dimitris (good to see you around ;) ),
>
> thing is… we want to improve our tools.
>
> And improve tools sometime means to add stuff (I’m not very happy with it
> either, I would like to remove more than what I add, but it is like t
hi Dimitris (good to see you around ;) ),
thing is… we want to improve our tools.
And improve tools sometime means to add stuff (I’m not very happy with it
either, I would like to remove more than what I add, but it is like that). For
example, if we want to have good class comments, we need so
Is it really necessary ?
I am more a modular guy , I would love to get an image that 0.1% the size
of the current one and offer me a convenient package manager to install the
tools I like.
I have used Pillar ALOT probably more than any other Pharo library because
I was doing Pharo documentation s
Even though I've initiated this discussion I kind of stopped reading because
everyone started discussing completely unrelated things...
The initial point was "we are using github/gitlab more and more, lets
leverage it more"
New, lets separate the concepts at play here...
"Pillar - document
Hi,
In general (you all know me), I have the policy of “do not go alien just
because” which means we do not need to reinvent the wheel all the time and we
need to stick with what is already there and known (I have pushed many changes
in pharo following this direction, iceberg being just the la
> On Aug 15, 2017, at 7:25 AM, Ben Coman wrote:
>
>
>
>> On Tue, Aug 15, 2017 at 12:54 AM, Esteban A. Maringolo
>> wrote:
>> You hit several birds with one single mail.
>>
>> 2017-08-14 13:34 GMT-03:00 Tim Mackinnon :
>> > Jimmie et al. nicely reasoned arguments - and Doru's point about
>
On Tue, Aug 15, 2017 at 12:54 AM, Esteban A. Maringolo wrote:
> You hit several birds with one single mail.
>
> 2017-08-14 13:34 GMT-03:00 Tim Mackinnon :
> > Jimmie et al. nicely reasoned arguments - and Doru's point about
> controlling
> > the syntax is an interesting one that I hadn’t thought
Hi,
> On Aug 14, 2017, at 3:51 PM, Esteban Lorenzano wrote:
>
> again, I think this is a discussion for pharo-dev.
> Please keep it there (is good discussion, btw ;) ).
>
> What about my proposal of including a tiny PetitParser? (it would be
> “InfimeParser” :P)
I am for it, but there will
Thank Tim,
My primary reason to submit the message was not to necessarily persuade
you per se. But to provide something historical for the mailing list as
this can be a recurring subject. Why use Pillar markup instead of
???(insert personal favorite).
If Pharo were to decide on a different m
We can change the syntax or propose an alternate one as soon as it
uses the same internal structure.
Stef
On Mon, Aug 14, 2017 at 6:34 PM, Tim Mackinnon wrote:
> Jimmie et al. nicely reasoned arguments - and Doru's point about controlling
> the syntax is an interesting one that I hadn’t thought
You hit several birds with one single mail.
2017-08-14 13:34 GMT-03:00 Tim Mackinnon :
> Jimmie et al. nicely reasoned arguments - and Doru's point about controlling
> the syntax is an interesting one that I hadn’t thought about.
>
> Personally, I find having too many similar syntax’s confusing -
Jimmie et al. nicely reasoned arguments - and Doru's point about controlling
the syntax is an interesting one that I hadn’t thought about.
Personally, I find having too many similar syntax’s confusing - contributing to
things is hard enough - having to remember that its !! Instead of ## and “”
TL;DR
Main points:
Their is no universally accepted markup language.
Other communities use their own markup and tools and their markup and
tools choice is not determine by other communities decisions.
We need a language and tool chain that we can control and maintain which
accomplishes our goa
again, I think this is a discussion for pharo-dev.
Please keep it there (is good discussion, btw ;) ).
What about my proposal of including a tiny PetitParser? (it would be
“InfimeParser” :P)
Esteban
> On 14 Aug 2017, at 11:10, Tudor Girba wrote:
>
> Hi Tim,
>
> The main benefit of relying
> On 12 Aug 2017, at 18:22, Guillermo Polito wrote:
>
> Esteban, I think that when Stef says "a mini version of pillar" he does not
> mean a mini version of the parser or the AST, but a version that does not
> have the exporting to html/latex/…
I know that.
But Cyril talked about “getting a
Esteban, I think that when Stef says "a mini version of pillar" he does not
mean a mini version of the parser or the AST, but a version that does not
have the exporting to html/latex/...
On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano
wrote:
> and btw, this kind of threads belongs to pharo-de
and btw, this kind of threads belongs to pharo-dev, not to pharo-users :)
Esteban
> On 12 Aug 2017, at 16:35, Esteban Lorenzano wrote:
>
>
>> On 12 Aug 2017, at 12:46, Tudor Girba wrote:
>>
>> Hi,
>>
>> I would very much like this path. What would constitute tiny?
>
> no idea, we need to t
20 matches
Mail list logo
