Fast and right would be ideal, but in the real (non ideal) world you have to use what is the best tool for the job. For mission critical applications where a tiny bit of speed can be sacrificed (eg banking, finance..etc) a no nonsense rock solid language like Java is ideal, especially with its rich ecosystem like Spring and JEE.
For others that are heavily I/O or R/W oriented like say a microblogging site with hundreds of thousands of users logging in and out and continually posting messages, multithreaded Java would not only slow things down but also hog resources (= high cloud services bill). This is where Node with its single threaded/ non-blocking nature would shine. Gab for example used to be on a more traditional platform like .Net or Java, I don't remember which. But as users spiked, especially after Trump was banned from Twitter, they started migrating to Node because Node was best at handling their specific use case. The more tools in your toolbox and knowing which to use when, the better.