Home > Interesting, python > The Case Against “The Case Against Python 3”

The Case Against “The Case Against Python 3”

View story at Medium.com

Advertisements
Categories: Interesting, python
  1. November 28, 2016 at 9:36 pm

    i wrote (but decided not to publish) a reply to “the case against python 3” that was more supportive of its basic conclusions… not all of them– the part that is basically conspiracy theory i remain skeptical of, though im not sure all parts of what shaw wrote were equally sincere in the first place.

    it was probably about as long as the article on medium, and i pointed out some of the errors and some of the things i agreed with, and why. im confident that this little debacle will get more people talking. im not also confident that google and guido will NOT go “oh! right, well lets just go back to python 2 then.” that will never happen. and its almost too bad.

    but the community wants python 3– that much im certain of. and the community cant honestly tell which changes are good and which are a shot to the foot, but this is mostly about strings and the fact that languages get (overly) complicated (bloated, with featuritis) with age. python 2 already seemed to have a “million” functions– if you count 3rd party libraries.

    i continue to strongly agree that python 2 is a simpler, more elegant, easier language. the fallacy (and false premise) that shaw is right to attack is this very “macho” as he puts its– “everyone competent has already switched, with good reason.” actually, no. its not true. most have moved on, to python 3 or to other languages, and the rest is just playing dirty. cue what the author (on medium) says about which language you should use– i think we all ultimately agree, we should use the language that suits the purpose.

    for shaw and myself (unless shaw is trolling, and he might be) thats probably python 2. for the guy i knew that worked at nokia, hes probably never going to switch either. if they every fork python 2, i think it would be pretty cool. python 3 will continue to chase fads and “evolve” as it were. hopefully, rpython is the incredible thing that makes the future of python not suck. i really hope something works out in the long run.

    • November 29, 2016 at 5:58 pm

      i think we all ultimately agree, we should use the language that suits the purpose.
      for shaw and myself (unless shaw is trolling, and he might be) thats probably python 2

      Exactly! Use the right tool for the job, not the latest fad.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: