3 ms·

Re-read the post. It seems like he _used_ to think Python was dead because he thought the Moratorium was implemented for different reasons than the actual rati

Re-read the post. It seems like he _used_ to think Python was dead because he thought the Moratorium was implemented for different reasons than the actual rationale. Now, I'm not sure if he still thinks Python is dead or not, but that's not what his post is about. He was just stating his opinion that Python has a "[...] fundamental design flaw: a syntax which requires human compilation."

wwortiz 17y ago
I did re-read the post and it just seems like perl 6 has reassured him that python is dying but I have to disagree, maybe jython is dead for what he wants but python is not dead and from the looks of it jython is not dead.
- andreyf 17y ago
  Err, I guess this teaches me to not to even mention simplistic emotional responses like "Python is dead". Let me try to be as clear is possible: Python is not dead. Python is hurting from a bad design decision that doesn't let multiple interpreter implementations share components that they could have. This makes it impossible for minimally maintained branches (like Jython) to keep up with the language, and so hard for better-maintained branches (like IronPython or pypy) that it necessitates a moratorium on the syntax as a whole.
  - wwortiz 17y ago
    I can understand where you are coming from and even though IronPython and other such things are interesting but from experience python is a much slower moving language, I still interact with systems using python 2.5 and I think the moratorium is a good thing for creating libraries and implementations and overall will make adoption quicker. I still think python's focus is in a slower world and as a python user I am okay with that.
  - fuzzyman 17y ago
    "Python is hurting from a bad design decision that doesn't let multiple interpreter implementations share components that they could have." As many others have said, changing syntax is really one of the most trivial parts for alternative implementations to keep up with when moving to new versions. That "hurt" hasn't been fixed because it doesn't really hurt very much...

wwortiz 17y ago

I did re-read the post and it just seems like perl 6 has reassured him that python is dying but I have to disagree, maybe jython is dead for what he wants but python is not dead and from the looks of it jython is not dead.

andreyf 17y ago
Err, I guess this teaches me to not to even mention simplistic emotional responses like "Python is dead". Let me try to be as clear is possible: Python is not dead. Python is hurting from a bad design decision that doesn't let multiple interpreter implementations share components that they could have. This makes it impossible for minimally maintained branches (like Jython) to keep up with the language, and so hard for better-maintained branches (like IronPython or pypy) that it necessitates a moratorium on the syntax as a whole.
- wwortiz 17y ago
  I can understand where you are coming from and even though IronPython and other such things are interesting but from experience python is a much slower moving language, I still interact with systems using python 2.5 and I think the moratorium is a good thing for creating libraries and implementations and overall will make adoption quicker. I still think python's focus is in a slower world and as a python user I am okay with that.
- fuzzyman 17y ago
  "Python is hurting from a bad design decision that doesn't let multiple interpreter implementations share components that they could have." As many others have said, changing syntax is really one of the most trivial parts for alternative implementations to keep up with when moving to new versions. That "hurt" hasn't been fixed because it doesn't really hurt very much...