On Jan 22, 9:43 pm, Tycon <[email protected]> wrote: > C is my expertise, but it can't match the productivity of python or > Ruby > Fortnately for C, it will always retain the performance crownm so it > will always have its uses > > The same thing cannot be said for python. Once its performance is once > its performance is matched by a > better language such as Ruby, python will be history. > > Python is so messed up, the only explanation is that the people making > it up are blindly following misguided principles. > The biggest lie/joke is that "there is only one way to do something > in python"
Hey! You can't talk about Python that way! Seriously, though, where'd you find that "quote"? > On Jan 22, 9:21 pm, Wyatt Baldwin <[email protected]> wrote: > > > On Jan 22, 8:21 pm, Tycon <[email protected]> wrote: > > > > I would gladly throw python away if only ruby matched its performance. > > > There's another option you may be interested, in case you haven't > > heard of it: C. It's *very* fast. > > > > On Jan 22, 3:48 pm, Wyatt Baldwin <[email protected]> wrote: > > > > > On Jan 22, 1:14 pm, Tycon <[email protected]> wrote: > > > > > > This is another example of the flawed, broken code known as "Paste". > > > > > Pylons should decouple itself from Paste > > > > > But Pylons, as you've pointed out, is flawed in numerous ways as well. > > > > Let's throw it *all* away! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
