Unveiling Ruby: Insights from Stack Overflow and Developer Survey

TL;DR

This study addresses the challenge of understanding Ruby developers’ difficulties by analyzing nearly half a million Ruby-related Stack Overflow questions with BERTopic-driven topic modeling and GPT-4o-assisted taxonomy construction, complemented by a 154-person developer survey. It yields a 35-topic taxonomy organized into six main categories and reveals that Web Application Development is the most discussed area while Gem Installation/configuration poses the greatest practical difficulty, with an overall decline in SO activity over time. A key finding is the misalignment between objective SO metrics and subjective developer perceptions, underscoring the need for improved metrics to capture real-world challenges. The work provides actionable insights for researchers and maintainers and opens up open data and code for reproducibility and broader ecosystem impact, while suggesting avenues for extending analyses to other platforms and leveraging AI tools.

Abstract

Ruby is a widely used open-source programming language, valued for its simplicity, especially in web development. Despite its popularity, with over one million users on GitHub, little is known about the issues faced by Ruby developers. This study aims to investigate the key topics, trends, and difficulties faced by Ruby developers by analyzing over 498,000 Ruby-related questions on Stack Overflow (SO), followed by a survey of 154 Ruby developers. We employed BERTopic modeling and manual analysis to develop a taxonomy of 35 topics, grouped into six main categories. Our findings reveal that Web Application Development is the most commonly discussed category, while Ruby Gem Installation and Configuration Issues emerged as the most challenging topic. Analysis of trends on SO showed a steady decline. A survey of 154 Ruby developers demonstrated that 31.6% of the participants find the Core Ruby Concepts category particularly difficult, while Application Quality and Security is found to be difficult for over 40% of experienced developers. Notably, a comparison between survey responses and SO metrics highlights a misalignment, suggesting that perceived difficulty and objective indicators from SO differ; emphasizing the need for improved metrics to better capture developer challenges. Our study provides insights about the challenges Ruby developers face and strong implications for researchers.

Figures (6)

• Figure 1: An overview of the methodology.
• Figure 2: Popularity vs Difficulty.
• Figure 3: Trends of six main categories over time. Blue: total number of category-specific questions over the years; Yellow: percentage of category-specific questions relative to all Ruby-related questions.
• Figure 4: Survey results of the difficulty levels divided by each category: (1)not difficult, (2)slightly difficult, (3)moderate, (4)difficult, (5)very difficult.
• Figure 5: Survey results of the required time to resolve issues divided by each category: less than $15$ min, between $15$ to $30$ min, between $30$ to $60$ min, between $1$ and $2$ hours, more than $2$ hours.