> The Rack web server interface from the Ruby community eventually made into python via the Flask application server and the WSGI specification. It's amazing h

> The Rack web server interface from the Ruby community eventually made into python via the Flask application server and the WSGI specification. It's amazing how just one sentence can be so utterly wrong. WSGI actually predates rack by several years: first WSGI spec was published in 2003 [0], rack was split from Rails in 2007 [1]. Flask is not an "application server", it is one of the web frameworks that implements WSGI interface. Another popular framework that also implements it is Django. Flask is not the first WSGI implementation, so I'm not sure why author decided to mention Flask specifically. It's probably one of the most popular WSGI implementations but there is nothing special about it, it hasn't introduced any new concepts or a new paradigm or anything like that. I'm not sure if the rest of the article is even worth reading if the author can't even get the basic facts right but for some reason feels the need to make up total nonsense in their place. [0] https://peps.python.org/pep-0333/ https://peps.python.org/pep-0333/ [1] https://github.com/rack/rack/blob/main/CHANGELOG.md https://github.com/rack/rack/blob/main/CHANGELOG.md