[Three things. Don't "yell" at me about languages. I don't care. If you have any valid reasons for why one is better at something than another, you still won't get an argument out of me -- If for no other reason than not having extensively used Perl or Python, I lack an opinion.
Secondly, I'm not learning a new language because there's something lacking in the languages I know. Sure, everyone has an "ifonly" list. Big deal. And to explain what I meant by "compelling" above... Python is fairly similar to UserTalk. I'm learning something new to expand what I understand. While Python may very well do that, it feels familiar enough that I'm concerned I won't get enough brain stretching out of it.
Lastly, I borrowed the term "spike" from XP, where it is used to refer to time spent "researching" something in order to provide a more accurate estimate. You drive a spike deeply into something... so the metaphor is that you learn enough about something you've never done before in order to help estimate how long it will take to build.
A "knowledge spike" is the same sort of thing. It's a page devoted to a single topic. It's not meant to be a directory, or inclusive or exclusive. It's links about a single possibly obscure topic that in the past would have filled up my home page for that day. Needlessly I think. Instead as I "spike" into various topics I'll create a "spike page", it'll keep things tidy and collected. ] *