Tech HR <[EMAIL PROTECTED]> writes: > No, it doesn't mean that. In fact, there is a significant faction in > the technical staff (including the CTO) who would like nothing better > than to be able to use Lisp instead of Python. But we have some pretty > compelling reasons to stick with Python, not least of which is that it > is turning out to be very hard to find Lisp programmers. (Actually, > it's turning out to be hard to find Python programmers too, but it's > easier to train a Java programmer or a Perler on Python than Lisp. We > also have fair bit of infrastructure built up in Python at this point.)
There's a lot of Python users around these days, and moving from Lisp to Python is very easy. The other way around is maybe a little harder but shouldn't be too bad. You know about http://lispjobs.wordpress.com I presume. Also: http://lemonodor.com and lambda-the-ultimate.org may have more pointers to such things. > But we're a very young company (barely six months old at this point) so > we're willing to listen to most anything at this point. (We're using > Darcs for revision control. Haskell, anyone?) Haskell is really a lot different and I think the implementations aren't as mature as Lisp or Python implementations. Maybe you want to think about SML or OCaml. -- http://mail.python.org/mailman/listinfo/python-list
