Uh... no. Ruby on Rails runs off a ruby webserver. Flask has its own built in webserver, web.py has its own built in webserver. Tho these are not languages, rather frameworks, (and in the case of web.py, a library), they have built in webservers

My point? These things came way before node.js, so no, node.js isn't the only one with a built in webserver.

The difference is node.js has a rather performant built in webserver (still, exeperience shows that a properly tuned gevent or netty beats a properly tuned node.js). The idea is that instead of spending time tuning these things, you can just wrap it in a uWSGI container, and let better tuned-out-of-the-box servers like nginx handle the webserving

In the sense of your statement, people are uncomfortable with compulsory concurrency for everything in Node.js off http not http itself.

Though you have to look at the package api yourself to decide whether it's running directly or not.