Comment by croemer

5 hours ago

There's a thread (now locked) on the Python discourse forum about the popup: https://discuss.python.org/t/accessibility-issues-in-the-pyp...

2 comments

croemer

Reply
quesera  4 hours ago

It's actually kind of embarassing seeing someone from the org chime in and say ~"this is our first time doing this, so we expected feedback" ... and separately infuriating ~"we will take this into account for next year".

  a) Any Internet-enabled human should have seen and avoided this problem from a million miles away.
  b) "We expected feedback" ?? this phrase is fucking insulting, sorry.
  c) Not next year. Take it down now and preserve some credibility. What is wrong with you people?

  • musicale  1 hour ago

    > What is wrong with you people?

    Unmitigated arrogance combined with scathing contempt for their user base, perhaps?

    I'd expect nothing less from the people that botched the Python 2.x to 3.x transition, burning billions of dollars of software value and countless hours of development effort in the process. Or the people who repeatedly failed to come up with a sane library and package system.

    Python demonstrates that having a standards body and caring about backward compatibility are not bad things, and that a platform's most important job is to absorb pain, not multiply it across millions of users.

    It comes as no surprise that even their web site would migrate to the latter camp.