<div dir="ltr">On Tue, Sep 30, 2008 at 5:01 PM, Alastair Johnson <span dir="ltr">&lt;<a href="mailto:alastair@truebox.co.uk">alastair@truebox.co.uk</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Nishit Dave wrote:<br>
&gt;<br>
&gt; &nbsp; &nbsp; *yawn* Predujice...<br>
&gt;<br>
&gt;<br>
&gt; *yawn* years of experience using yumex, Fedora and what not. &nbsp;Carefully<br>
&gt; considered Predijuice.<br>
<br>
</div></div>Can you point to something specific that makes python unsuitable for a<br>
responsive GUI? I&#39;ve seen unresponsive GUIs written with many languages,<br>
but it is generally a problem with the code not the language.<br>
<div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote></div><br>How about experience? I don&#39;t know about programming or system specifics, but as a user, I have always found most programs written in python to be prone to latency in screen redraws and freeze-ups.&nbsp; You can test that on the FR - just try Mofi, switch to say the home screen, and switch back.&nbsp; You will be able to see how long it takes before text appears.&nbsp; I have seen this happen everywhere.<br>
<br>Just from an efficiency point of view, don&#39;t you think a compiled program may run better than an interpreted one on a system with limited hardware capabilities.<br><br>Anyway, why do I bother...<br></div>