Hello Serge
https://ummisco.github.io/kendrick/
https://github.com/UMMISCO/kendrick
:-)
Maybe you can refer to a report how it was used?
--Hannes
On 10/14/17, Serge Stinckwich wrote:
> On Sat, Oct 14, 2017 at 11:50 AM, H. Hirzel
> wrote:
>
>> On 10/12/17, Andrew Glynn wrote:
>> > https://me
On Sat, Oct 14, 2017 at 11:50 AM, H. Hirzel wrote:
> On 10/12/17, Andrew Glynn wrote:
> > https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034
> > c71
> > This is an article not specifically about Pharo, rather on the state of
> > the industry
> > in general and how it got tha
On 10/12/17, Andrew Glynn wrote:
> https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034
> c71
> This is an article not specifically about Pharo, rather on the state of
> the industry
> in general and how it got that way, but positing Pharo as a way to
> learn
> building-on rathe
The problem is that it takes 1233 pages of config, and that's the summary
page of my config, and it uses 15GB RAM, on my laptop, lol.
On Sat, Oct 14, 2017 at 1:10 AM, jtuc...@objektfabrik.de <
jtuc...@objektfabrik.de> wrote:
>
>
> Am 12.10.17 um 20:04 schrieb Dimitris Chloupis:
>
>>
>> Eclispe ,
I stand corrected
On Sat, 14 Oct 2017 at 08:11, jtuc...@objektfabrik.de <
jtuc...@objektfabrik.de> wrote:
>
>
> Am 12.10.17 um 20:04 schrieb Dimitris Chloupis:
> >
> > Eclispe , which I will disagree with your that is not the worst IDE,
> > started as a smalltalk IDE and then it got Eclipsed. I a
Am 12.10.17 um 20:04 schrieb Dimitris Chloupis:
Eclispe , which I will disagree with your that is not the worst IDE,
started as a smalltalk IDE and then it got Eclipsed. I am sure those
people had a "build on" environment , still it got messy. We can blame
porting to Java, but can we really
Hi Andrew, Stephane,
thanks for the read. It was interesting, albeit a bit confusing at times. I
do like your evaluation of the thesis.
2017-10-12 23:10 GMT+02:00 Stephane Ducasse :
> Thanks Andrew I read it fast and I will reread it. It is really
> interesting to me because I never took the tim
s 10
>
>
>
> *From: *Dimitris Chloupis
> *Sent: *Thursday, October 12, 2017 2:05 PM
> *To: *Any question about pharo is welcome
> *Subject: *Re: [Pharo-users] "Building-With versus Building-on"
>
>
>
> It's a mentality issue, modern programming lan
: Dimitris Chloupis
Sent: Thursday, October 12, 2017 2:05 PM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] "Building-With versus Building-on"
It's a mentality issue, modern programming languages provide the material
necessary to create innovative environments but th
Thanks Andrew I read it fast and I will reread it. It is really
interesting to me because I never took the time to understand "worse
is better".
On Thu, Oct 12, 2017 at 5:50 PM, Andrew Glynn wrote:
> https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034c71
>
>
> This is an artic
It's a mentality issue, modern programming languages provide the material
necessary to create innovative environments but their communities just
simply does not care. A language designer may introduce a feature in a
language that is super useful. Still people may not use it.
And let's face it even
Thanks for posting this.
It is one of the best descriptions of the state of the software industry
that I have seen.
On Thu, Oct 12, 2017 at 11:50 AM, Andrew Glynn wrote:
> https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034c71
>
>
> This is an article not *specifically* abo
https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034
c71
This is an article not specifically about Pharo, rather on the state of
the industry
in general and how it got that way, but positing Pharo as a way to
learn
building-on rather than building-with, where in the latter case o
13 matches
Mail list logo