[Pharo-dev] Responsible development
Benjamin.VanRyseghem.Pharo at gmail.com
Mon Dec 2 14:08:50 EST 2013
We try now to have responsive UIs in the sense the tools like Nautilus try to
run things in a separate thread.
I will do an experiment and fork each Nautilus opening to see if it can save my ass :P
On 02 Dec 2013, at 19:59, Yuriy Tymchuk <yuriy.tymchuk at me.com> wrote:
> On 02 Dec 2013, at 17:42, Sean P. DeNigris <sean at clipperadams.com> wrote:
>> Uko2 wrote
>>> It’s not about stability of pharo 3, it about concurrency... This thread
>>> doesn’t seem to have any reason
>> Nothing is wasted. I appreciate your ideas. I never thought of these
>> benefits; I always took it for granted to run in one thread.
> Even if everything runs in one thread it doesn’t mean that you need to block something. And I know that example with Nautilus or even with test runner may be to hard.
> Let’s take moose for example. While it is importing a model everything freezes. Is there a reason for that? I don’t see any. In my opinion the problem is that we are not used to run non-instant operations in a separate process, because I do a lot of mistakes like this too.
>> View this message in context: http://forum.world.st/Responsible-development-tp4726686p4726763.html
>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev