I also agree that making "lower level" bindings can leave the API a bit shady (Akka's[1] Java version is a bit uglier due to lack of Anonymous Functions, which have to be replaced by Interfaces).
About example of frameworks which more popular in another language, I honestly can't think of few other than Akka. I admit is uncommon for frameworks to support its host language (in a multi-language platform), and host languages are usually much more crowded than their sub-language counterparts.
What happens far more frequently is a complete re-implementation on the host language, example: instead of using JRuby on Rails, people migrate to Play framework[2]
Hadoop[3], however, seems to be getting really tracktion from its other language bindings[4], as writing map-reduce tasks in Java is not fun at all.
About example of frameworks which more popular in another language, I honestly can't think of few other than Akka. I admit is uncommon for frameworks to support its host language (in a multi-language platform), and host languages are usually much more crowded than their sub-language counterparts.
What happens far more frequently is a complete re-implementation on the host language, example: instead of using JRuby on Rails, people migrate to Play framework[2]
Hadoop[3], however, seems to be getting really tracktion from its other language bindings[4], as writing map-reduce tasks in Java is not fun at all.
[1] http://akka.io/
[2] http://www.playframework.org/
[3] http://hadoop.apache.org/
[4] http://pig.apache.org/