Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why not Python?

Name: Anonymous 2008-06-27 15:32

What's wrong with Python?

Name: Anonymous 2008-07-10 7:40

The problem with this is that there is actually a difference in the usage of hue and colour - we mostly use hue to distinguish it from the other meanings of ``colour''.
how about blee then?
http://en.wiktionary.org/wiki/blee

Name: Anonymous 2008-07-10 8:06

Weeaboo quotes

Name: Anonymous 2008-07-10 8:09

>>82
「Weeaboo Quotes」

Name: Anonymous 2008-07-10 9:00

>>83
This capital Q is very beautiful and I feel kind of happy about it :)

Name: Anonymous 2008-07-10 9:02

>>81
Is this the root word of bling?

Name: Anonymous 2008-07-10 11:30

>>85
blee, bling, blaught

Name: Anonymous 2008-07-10 11:33

Quality `Q'.

Name: Anonymous 2008-07-10 11:50

Name: Anonymous 2008-07-10 11:54

What's wrong with Python?

Name: Anonymous 2008-07-10 12:51

>>83
「ウィーアブークォテス」

Name: Anonymous 2008-07-10 12:57

>>90
Read 「計算機プログラムの構造と解釈」.

Name: Anonymous 2008-07-10 13:37

´´Saging the ¡top! 'thread' «quotes»´´

Name: Anonymous 2008-07-10 17:11

>>91
Computer Program no Structure to Interpretation?

CPのSI?

Name: Anonymous 2008-07-10 18:43

>>93
Moonspeak is abbreviated by just taking the first syllable of each word.

And not translating it into english.

Name: Anonymous 2008-07-12 3:49

>>94
Read keipukōkai.

Name: Anonymous 2008-07-12 12:08

>>2
Fag

>>3
Probably, because he doesn't like FP.

>>6
Note "obvious". There are infinite non-obvious ways, just like in Science.


>>9
You can use braces in Python too:
if a < 1: #{
    print 'hello'
#}


>>11
You could have said Ruby is nasty, Ruby looks like vomit, Ruby's operators are insane, Ruby is not clean like a Lisp-1, etc., but slow? That's the stupidest reason ever. Also, check out alternative Ruby interpreters.

Name: Anonymous 2008-07-12 12:28

>>96
Probably, because he doesn't like FP.
When did he actually do something to make Python less FP-friendly that it had previously been? Python lambdas were always shitty (and in my opinion, should be removed entirely), and moving some useless crap to functools doesn't count (Python has list comprehensions).

>>11
You could have said Ruby is nasty, Ruby looks like vomit, Ruby's operators are insane, Ruby is not clean like a Lisp-1, etc., but slow? That's the stupidest reason ever. Also, check out alternative Ruby interpreters.
I'm not >>11, but one of my main reasons for replacing my Ruby use with Python a couple of years ago was the fact that it indeed was glaciously slow. Even the simplest things like reading shitloads of data from a file into simple data structures (which should, and in any properly implemented language, is, IO-bound) were mindblowingly slow in Ruby, even when my code basically gave a blowjob to Ruby's garbage collector.

Your other points about Ruby are valid, though.

Name: Anonymous 2008-07-12 12:50

glaciously
Did you mean: glacially

Name: Anonymous 2008-07-12 12:56

>>98
In fact, I did.

Name: Anonymous 2008-07-12 12:59

100GET
The ABC Programming Language

Name: Anonymous 2008-07-12 17:25

>>97
Crippled lambdas and refusal to optimize tail calls1 to name a short few.

[1] - http://mail.python.org/pipermail/python-dev/2004-July/046171.html

Name: Anonymous 2008-07-12 17:37

>>101
Python lambdas have always been crippled like I said.

About the tail call thing, you seem to be right. He may have a point about stack traces, but his other argument seems to be plain FP-bashing.

Still, Python continues to be the language I end up using the most in the real world. It doesn't actively suck in most cases, and there is a huge amount of useful libraries for actually getting the thing done, right now.

Name: Anonymous 2008-08-03 20:19

bump

Name: Anonymous 2008-08-04 13:20

A while back I decided to check out this thing called Python that everyone was praising. Thought it was kinda neat at first... until I found out it had FIOC, at which point I uninstalled everything related to it.

Most stupid idea since... well, I really can't think of anything worse ever being introduced in a language before. 99% of the time it achieves absolutely nothing because people indent properly anyway for readability. And the rest of the time there's usually a good reason breaking convention.

Not to mention the joy of trying to track down a runtime bug caused by a missing/extra tab in a large project. Whee.

Seriously... just... WHY?!

Name: Anonymous 2008-08-04 13:48

Not to mention the joy of trying to track down a runtime bug caused by a missing/extra tab in a large project. Whee.
I've been using Python for years in large ENTERPRISE-scale projects and have never encountered this problem. I suspect you are using a sub-standard editor. Might I recommend some vim?

Name: Anonymous 2008-08-04 13:52

I agree with >>105.

Name: Anonymous 2008-08-04 14:14

This was a nice discussion about Python.

Name: Anonymous 2008-08-04 21:10

>>104
Ed may be the standard, but you should really learn to use better text editors to help you input and study your programming code. Emacs and Vim may take up more computer resources, but in this day and age, computers have enough resources to handle these programs.

Name: Guido van Rossum 2008-08-05 19:58

Very few open source languages have been formally specified. Formal language specifications seem to be particularly attractive when there is a company that wants to exercise control over the a language (such as for Java and JavaScript), or when there are competing companies that worry about incompatible implementations (such as for C++ or SQL).

Name: Anonymous 2008-08-05 20:01

Python: For and by micromanagers.

Name: Anonymous 2008-08-05 21:42

Guido works at Google.  Google does a lot of stuff with Python.  Certainly, no coincidence there.

Name: Anonymous 2008-08-05 22:18

Let's get back to the discussion about ``quotes''.

Name: Anonymous 2008-08-06 10:42

python is the shit yo. i can wank out code quicker in python than i can wank myself off, it's pretty good just for getting stuff done.

you can always write it better in a faster language later if performance is an issue

Name: Anonymous 2008-08-06 10:59

ONE REASON, FORECD INDENTIOAN OF CODE, THREAD OVER!!!!!!!

Name: Anonymous 2008-08-06 13:11

>>113
You're doing it wrong.

Name: Anonymous 2009-03-06 13:55

Wian 99 verb or sup b 66.

Name: Anonymous 2010-10-27 2:27

Name: Anonymous 2010-11-25 10:45

Name: Anonymous 2011-02-03 0:10


Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List