How coding in Python is bad for you
BartC
bc at freeuk.com
Mon Jan 23 16:55:01 EST 2017
More information about the Python-list mailing list
Mon Jan 23 16:55:01 EST 2017
- Previous message (by thread): How coding in Python is bad for you
- Next message (by thread): How coding in Python is bad for you
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 23/01/2017 17:34, Chris Angelico wrote: > On Tue, Jan 24, 2017 at 4:24 AM, <breamoreboy at gmail.com> wrote: >> The article is here http://lenkaspace.net/index.php/blog/show/111 > > I would respond point-by-point if I thought the author had a clue. I thought points 1 to 4 were valid, in that the assertions were true. Point 5 (memory leaks) I haven't experienced. Point 6 (libraries depending on libraries...) is probably true in other languages too. Point 7 (Python claiming to be general purpose) I don't have an opinion about. -- Bartc
- Previous message (by thread): How coding in Python is bad for you
- Next message (by thread): How coding in Python is bad for you
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list