[coreyp_1]

You never "screw up" by learning. For that matter, you learned a lot about javascript and asynchronous programming. Furthermore, you would probably now (more than the average programmer) appreciate the advances of ES6 and the promises/generator pattern.

As for what you "should" be using, there is no right or wrong answer. The biggest metric is whether or not the language is a good fit for the task. The only thing that JS is bad at, IMO, is CPU-intensive tasks. Aside from that, it may be perfectly adequate for the job.

The only other factors would be if there were a language that offered features (or libraries) that you need.