On Fri, 10 Mar 2017 20:38:27 +0100, Nicolai Hess <[email protected]> wrote:



2017-03-10 20:18 GMT+01:00 stepharong <[email protected]>:
Torsten

Why are you full of bad energy?
Having a setting is perfectly ok. Why all this bad energy.

The problem is not having a setting, the problem is to have *two* distinct settings for the same thing.

Yes and this can be fixed to have only one.
I do not see the problem.
And I'm in favor to have one and I was never against it.

Stef





Do you think that this is nice to hear that I push solution for fucking african idiots?
I spent so much time writing and producing solutions for newbies.
I just spent three months fixing the Pharo by example book and THIS IS NOT MY JOB. Do you think that writing a full mooc that we can use to promote Pharo all over the world is not important? I was not in the mood to write it. For my CV a mooc is nothing.
Zero impact.
You see when people evaluate my CV I got feedback like
"stephane is a brillant researcher but he is focusing too much on poor languages."
And many other things.
So now you can be aggressive and pissed. I decided long time ago that I do Pharo for positive
energy. Now if you do not like what I'm doing I cannot do much.

Stef




Uko wrote:
If there is a rule not to duplicate preferences, why is catalog not following it?

Because at the time when I implemented it for catalog there was no other setting.

The enabling/disabling for all GT extension was introduced later. Also the confusing default was introduced later (with the more hidden spotter extension disabled and
leaving the Catalog setting enabled) leading to this whole mess.

To be honest I dont care or respond anymore on the whole issue because as we now know from
the long discussion the only outcome is that:

<sarcasm>
- most of us should be knowledgable enough to know that two settings exist - most of us should become experts in fixing deficencies with startup scripts - most of us should accept that we have to hide features as deep as possible in the settings tree - most of us should accept that we have to make it as complicated as possible to load catalog projects - most of us should accept that we can display and access anything in spotter except catalog projects - most of us should accept that Pharo videos get broken and never match reality
 - most of us should continue to "rest in their comfort zone"
- most of us should continue to be "an egoist instead of being an adult" - most of us should be allowed to speak up only when they presented Pharo at a university
 - most of us should start working with slow networks
</sarcasm>

Fixing it by removing Spotter and Catalog completely from Pharo would possibly be the
best solution. Anyone up for a slice?

Bye
T.



--Using Opera's mail client: http://www.opera.com/mail/





--
Using Opera's mail client: http://www.opera.com/mail/

Reply via email to