These are all cursory details of JS using something like Node on the backend. All of which are factually accurate sure, but don’t really tell a complete story. None of these I would list as concerns when starting a new backend project in JS. Things like cohesion, interoperability with the data layer and other services, and real testability are the real struggles with using JS on the backend. These are the things that developers are going to run into. The obstacles that will slow them down, cause errors/bugs, and require a lot more attention than they really need to. What isn’t really possible in JS as a backend server is:
rails new project rails g scaffold DataType rails db:migrate rails server
And that’s gonna cost you and the other developers a lot of time and effort on maintenance and away from your core business logic. Not really a good trade off.