Re: [Pharo-project] Slow text input?
I NEVER had an image crash, of course i'm not stating that it cant crash, but would be nice to know how many people have to deal with image crashes and how often. Because, up to now, during my last 3 years of Pharo usage it never has been a big issue for me. Fernando On Tue, Nov 15, 2011 at 1:37 PM, Peter Hugosson-Miller <oldmanlink@gmail.com> wrote:
I think the troll said he was leaving, so let's just all take a deep breath, be thankful for that, and move on.
Positive energy is what we need here, feeding trolls drains us more than one would think, so as far as possible we should just try and ignore them.
Carlo's answer was cool, too ;-)
-- Cheers, Peter
On Tue, Nov 15, 2011 at 1:26 PM, Igor Stasenko <siguctua@gmail.com<mailto:siguctua@gmail.com>> wrote: Currently, my Mac running 3 images. And it is hard to tell, but i think one of them runs maybe more than month , without hangs, freezes etc. Now, why i should trust your words (not backed with anything serious) that the software i use is unstable, when i using it every day and it works well for me?
On 15 November 2011 12:18, Guido Stepken <gstepken@googlemail.com<mailto:gstepken@googlemail.com>> wrote:
Ok, if it helps you to understand, that unstable software is quite useless for anybody ... will do that!
Guido Stepken
Am 15.11.2011 um 12:05 schrieb Marcus Denker <marcus.denker@inria.fr<mailto:marcus.denker@inria.fr>>:
On Nov 15, 2011, at 8:00 AM, Guido Stepken wrote:
I think, programming, refactoring a peace of software has very much to do with model theory, Löwenheim-Skolem theory (related to fixed point theorem).
Good programmers migrate code, addon's from one stable, consistent state to the other. These "stable states" are expressed in release numbers.
What are you doing? Don't know!
So why don't you then just unsubscribe from the mailinglist?
We clearly are not up to your standards. And this will not change.
I think there is no way that we can work constructively together, so the best for all is that you just go away. and everyone is happy. (you, too!)
You can refactor according to Skolem, we refactor how we like it, and everyone is happy.
  Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko.
On 15 Nov 2011, at 13:48, Fernando Olivero wrote:
I NEVER had an image crash, of course i'm not stating that it cant crash, but would be nice to know how many people have to deal with image crashes and how often.
In the course of one week: $ grep STARTUP MyImage.35.changes | grep MyImage | wc -l 45 What does that mean? I started the image 45 times. And, no, I did not frequently save and quit the image, I just made it crash/unusable one way or another. How to deal with it? $ grep SNAPSHOT MyImage.35.changes | grep MyImage | wc -l 145 But, well, what I did is certainly uncommon usage scenario. People usually do not change #basicNew/#basicNew: or the Parser/Compiler/Encoder classes. So much for numbers Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
Indeed stfan and I would like to get the system even more robust to that kind of changes. In fact I would like to get a new class builder and a bootstrap but now I spent my day in meetings, writing reports and losing energy. Stef
I NEVER had an image crash, of course i'm not stating that it cant crash, but would be nice to know how many people have to deal with image crashes and how often.
In the course of one week:
$ grep STARTUP MyImage.35.changes | grep MyImage | wc -l 45
What does that mean? I started the image 45 times. And, no, I did not frequently save and quit the image, I just made it crash/unusable one way or another.
How to deal with it?
$ grep SNAPSHOT MyImage.35.changes | grep MyImage | wc -l 145
But, well, what I did is certainly uncommon usage scenario. People usually do not change #basicNew/#basicNew: or the Parser/Compiler/Encoder classes.
So much for numbers Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
I had a funny crash when I did Editor := 'editor' in a class using a sharedPool with a class variable named Editor Now this is fixed in 1.4 but what we should do is to get the revert last accept in the emergency evaluator working again :) Stef On Nov 15, 2011, at 1:48 PM, Fernando Olivero wrote:
I NEVER had an image crash, of course i'm not stating that it cant crash, but would be nice to know how many people have to deal with image crashes and how often.
Because, up to now, during my last 3 years of Pharo usage it never has been a big issue for me.
Fernando
On Tue, Nov 15, 2011 at 1:37 PM, Peter Hugosson-Miller <oldmanlink@gmail.com> wrote:
I think the troll said he was leaving, so let's just all take a deep breath, be thankful for that, and move on.
Positive energy is what we need here, feeding trolls drains us more than one would think, so as far as possible we should just try and ignore them.
Carlo's answer was cool, too ;-)
-- Cheers, Peter
On Tue, Nov 15, 2011 at 1:26 PM, Igor Stasenko <siguctua@gmail.com<mailto:siguctua@gmail.com>> wrote: Currently, my Mac running 3 images. And it is hard to tell, but i think one of them runs maybe more than month , without hangs, freezes etc. Now, why i should trust your words (not backed with anything serious) that the software i use is unstable, when i using it every day and it works well for me?
On 15 November 2011 12:18, Guido Stepken <gstepken@googlemail.com<mailto:gstepken@googlemail.com>> wrote:
Ok, if it helps you to understand, that unstable software is quite useless for anybody ... will do that!
Guido Stepken
Am 15.11.2011 um 12:05 schrieb Marcus Denker <marcus.denker@inria.fr<mailto:marcus.denker@inria.fr>>:
On Nov 15, 2011, at 8:00 AM, Guido Stepken wrote:
I think, programming, refactoring a peace of software has very much to do with model theory, Löwenheim-Skolem theory (related to fixed point theorem).
Good programmers migrate code, addon's from one stable, consistent state to the other. These "stable states" are expressed in release numbers.
What are you doing? Don't know!
So why don't you then just unsubscribe from the mailinglist?
We clearly are not up to your standards. And this will not change.
I think there is no way that we can work constructively together, so the best for all is that you just go away. and everyone is happy. (you, too!)
You can refactor according to Skolem, we refactor how we like it, and everyone is happy.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko.
participants (3)
-
Fernando Olivero -
Stefan Marr -
Stéphane Ducasse