> Richard Robinson <rich...@privacy.net
> wrote in
>> You mentioned Python before, and I nearly bit (back ? uncomfortable
>> image, there), and so this time I will, that I started looking at that
>> last winter, after a few decades of Perl. First impression, a flat-out
>> determination to be the exact opposite. Swings & roundabouts, of
>> course, but feels excessively lacking in all the little conveniences.
>> Tedious and restrictive to write, expensive on the ingers & eyes, but
>> the result somehow adds up to a very nice clean structure.
>> Whitespace-dependent syntax offers a whole new category of
>> hard-to-spot mysteries.
> I use Python mainly because of the Idle IDE, which just works with very
> little effort and largely takes care of the whitespace nonsense.
Ah; I've noticed refs to it, but - again, habits from other languages -
Kate's a convenient editor for lots-of-files-open, and then run the
hooter with much logging.debug("Clutter"). I'll hope to get tuitted up
to have a look, ta.
> I find that when I start looking at a new language I seem to focus first on
> all the ways it is inferior to the languages I am used to. If I can get
> through that stage I can start to find the good bits, and sometimes that is
> enough to convert me. I couldn't get on with Perl, or Ruby for that matter,
> but I guess that I would grow to love them idc if I persevered. Life's too
> short. One day I'll dust down my old C++ compiler, if I can find a suitable
The last Microsoft stuff I ever touched was Visual C++ v1 on w3.1 over
Dos5. Then I developed a very deep need for the TeX toolchain and a
psotscript interpreter, and slackware linux over a slow modem looked
like a more promising approach, given the GNU docs' attitude to
compiling such things in Dos. ISTR the absence of a fork() was mentioned
with a certain air of disapproval ... the way that I'd paid a chunk of
zbarl for something wonderful, and was subsequently contacted not all
that much later with the revised info that it was actually a pile of
steaming donkeypoo (to borrow from a fiend round here) that would
require another input of zbarl which would of course turn it into all
the things that I'd expected of the last one looked like the sort of
potentially-infinite loop best broken out of by Free Software, too.
> Has it? I didn't know. I use Tk but find it difficult these days to
> remember all the finctions and how to call them. I had a go with Guizero
> recently - it's a wrapper around Tk. Makes it more user friendly, but I
> found it a bit limmited.
I want windowy things for various reasons at various times, and Tk
always seemed the simplest, until the dependence on seriously old
libraries became too much of a stopper; but it's allright noow. tkinter
is the Python wrapper, and *that*'s limited. More tuits for Guizero,
someone, please ? I'd never heard of it. Again, ta.