🚀 go-pugleaf

The problem with making these decisions is that most non-programmers (and
lots of programmers too) don't look any further than speed.  Speed just
happens to be the easiest (to the naive) thing to measure, and the most
obvioous "good thing".  I think the whole software lifetime needs to be
examined.  Is this program only going to be used once?  Do you expect to
have tens of thousands of users?  Do you intend to reimplement it?  Will
you have to reimplement it when you need to add that unforseen feature?
How long will it take to design? How long will it take to implement?  Of
course you won't know the answer to most of these questions when you're
deciding whether to use lisp, C or BASIC, but you need to ask them to give
some perspective.  

Of course the most important thing is that the software exists and
that it does what was wanted.  It is hard to look beyond the initial
implementation, but maintainability and extensibility can be important.
It is a mistake to get too caught up with speed at the expense of other
factors.