I will add to the chorus of "yes, it's OK" answers but want to draw your attention to the more personal nature of Code Review - not only can you present two questions with the same problem, solved in different languages, but you can even post two questions with the same problem in the same language.

Specifically, on Code Review you are encouraged to take the suggestions given in one answer, apply as much as you feel necessary to your code, add your own modifications and then present the revised code again for review. Subsequent reviews can confirm your changes made sense, and if the changes make other problems more apparent, you may get further insights or suggestions.

This "follow on" nature is described well in this editing-related meta post.

So, take what you learn in one place, apply it again, or differently in another, and post the result or review.... rinse, and repeat.

I will add to the chorus of "yes, it's OK" answers but want to draw your attention to the more personal nature of Code Review - not only can you present two questions with the same problem, solved in different languages, but you can even post two questions with the same problem in the same language.

Specifically, on Code Review you are encouraged to take the suggestions given in one answer, apply as much as you feel necessary to your code, add your own modifications and then present the revised code again for review. Subsequent reviews can confirm your changes made sense, and if the changes make other problems more apparent, you may get further insights or suggestions.

This "follow on" nature is described well in this editing-related meta post.

So, take what you learn in one place, apply it again, or differently in another, and post the result or review.... rinse, and repeat.