All of which is beside the point. Those servers are (even in the documentation) not suggested to be used in production. And they are not.
Whereas Go's server serves thousands of requests per second in large deployments already.
The only other I know of is perhaps Node.
So, yes, seriously.
As such, I consider it as much a platform as it also is a version of the Javascript language for the backend.
Languages ARE platforms anyway -- we never care just about their core syntax and semantics but also for all the libs stuff they come with. So Python includes batteries, and Java includes the kitchen sync.
But you're also wrong in suggesting that Python's built-in webservers are equivalent to Golang's. What's the largest deployed Python application that uses those servers? My understanding is that every deployed Golang app uses net/http.
> Python has SimpleHTTPServer
And Ruby has WEBrick.
Erlang comes with one in the standard inets library.
Racket has one, too, in the standard distribution (it doesn't actually use, that I am aware of, the "standard library" name, and given the structure of the documentation one might argue that the web server is outside of the standard library, but I'm not sure that is a significant distinction.)
Web servers as part of the standard library or distribution are pretty common for languages these days.
Otherwise the articles more or less on point.
Seriously?
Python has SimpleHTTPServer to serve a directory plus the associated, less-well-known modules BaseHTTPServer (which SimpleHTTPServer is based on) and CGIHTTPServer, and wsgiref as the reference implementation of the WSGI interface, which makes it a fully-fledged web server.
And I find it impossible to believe that there would not be many more languages with a web server in their standard libraries.