Want a New Pony?
Tim’s not quite right about Python programmers; in reality, it’d break down like this:
- 49% would recommend submitting a PEP for a Python Pony Protocol, which would take approximately five and a half years to be reviewed, commented on, implemented as a proof of concept, reviewed again, commented on some more and finally buried in peat moss.
- 50% would point out that Python already provides the necessary infrastructure for ponies, but likely wouldn’t provide any examples of how to take advantage of it.
The remaining one percent would be split among:
-
People who point out that with IronPython you could just use the built-in
System.Horse.Ponyclass from .NET. -
People who point out that with Jython you could just use the built-in
java.lang.Horse.Ponyclass from Java. -
People who point out that asynchronously generating ponies is much easier in Twisted, once you wrap your head around the idea of needing to put your foot in the stirrup and mount the
Ponybefore you call the code to create it. - Guido, who’d just say, “I like ponies”.
Now, where did I leave my asbestos suit?
Comments for this link are closed. If you'd like to share your thoughts on this link with me, please contact me directly.