mlsanityData to 7 Oct 2026

Bridging the Language Gap: An Empirical Study of Bindings for Open Source Machine Learning Libraries Across Software Package Ecosystems

arXiv 2201.07201 ↗First posted 18 Jan 2022cs.SE cs.LGcited by 2

Not on the map. Why?

Abstract (arXiv)

Open source machine learning (ML) libraries enable developers to integrate advanced ML functionality into their own applications. However, popular ML libraries, such as TensorFlow, are not available natively in all programming languages and software package ecosystems. Hence, developers who wish to use an ML library which is not available in their programming language or ecosystem of choice, may need to resort to using a so-called binding library (or binding). Bindings provide support across programming languages and package ecosystems for reusing a host library. For example, the Keras .NET binding provides support for the Keras library in the NuGet (.NET) ecosystem even though the Keras library was written in Python. In this paper, we collect 2,436 cross-ecosystem bindings for 546 ML libraries across 13 software package ecosystems by using an approach called BindFind, which can automatically identify bindings and link them to their host libraries. Furthermore, we conduct an in-depth study of 133 cross-ecosystem bindings and their development for 40 popular open source ML libraries. Our findings reveal that the majority of ML library bindings are maintained by the community, with npm being the most popular ecosystem for these bindings. Our study also indicates that most bindings cover only a limited range of the host library's releases, often experience considerable delays in supporting new releases, and have widespread technical lag. Our findings highlight key factors to consider for developers integrating bindings for ML libraries and open avenues for researchers to further investigate bindings in software package ecosystems.

Key facts. Cited by 2 papers in the map (data through 7 Oct 2026). Builds on 13 of its 89 references that are in the map. First posted on arXiv 18 Jan 2022.

Builds on

13 of 89 references.

References · 13

  1. 2018BERT: Pre-training of Deep Bidirectional Transformers for Language Understandingcited by 40,204
  2. 2019PyTorch: An Imperative Style, High-Performance Deep Learning Librarycited by 20,160
  3. 2019RoBERTa: A Robustly Optimized BERT Pretraining Approachcited by 13,266
  4. 2019DistilBERT, a distilled version of BERT: smaller, faster, cheaper and lightercited by 4,243
  5. 2016SQuAD: 100,000+ Questions for Machine Comprehension of Textcited by 4,115
  6. 2019ALBERT: A Lite BERT for Self-supervised Learning of Language Representationscited by 2,772
  7. 2018Know What You Don't Know: Unanswerable Questions for SQuADcited by 1,538
  8. 2019An Empirical Study towards Characterizing Deep Learning Development and Deployment across Different Frameworks and Platformscited by 35
  9. 2019TensorFlow.js: Machine Learning for the Web and Beyondcited by 29
  10. 2016Understanding the Factors that Impact the Popularity of GitHub Repositoriescited by 27
  11. 2019What Do Developers Ask About ML Libraries? A Large-scale Study Using Stack Overflowcited by 13
  12. 2017An Empirical Comparison of Developer Retention in the RubyGems and npm Software Ecosystemscited by 4
1 more
  1. 2018Breaking the borders: an investigation of cross-ecosystem software packagescited by 1

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2026: 2.

2 papers.