TUNES and Python

[Tom Novelli]

  I'd grown skeptical of this whole TUNES project, until recently when a
friend encouraged me to look at Python (a language I'd previously ignored as
"too slow").  I'm impressed with the overall _practicality_ of it, even if
it is slow.  And in the years I was ignoring Python, Armin Rigo here wrote a
compiler for it and solved the speed problem (although that's not enough to
replace C and Assembler for all low-level programming).  Maybe I'm speaking
too soon (I haven't written any substantial Python programs yet) but so far,
I like it!
  I couldn't help noticing the parallels between what TUNES aims to be and
what Python already is.  The main difference I see is perfectionism versus
pragmatism.  I say, so what if Python programs aren't provably safe and
correct?  This language makes programming more manageable for people we tend
to think of as "users" (engineers for example).  Dispelling the user
illusion - isn't that the ultimate goal?  This opens up the possibility that
large all-purpose software packages will give way to small custom-made
programs, which could drastically reduce the amount of complex intertwined
code in use. Not that it's a panacea.  It just might usher in a new wave of
sloppily written software (if it's possible to sink any lower than the
current state of affairs!)  And it would ruin some big software companies,
but it's hard to feel sorry for people who made fortunes by taking away
regular peoples' jobs!
  Anyway, I just wanted to put in a good word for a change.  Maybe TUNES
itself will never take shape, but good things are emerging out of all the
interplay.