The State of Ruby Dev Tooling

### Key Points: **The Complexity of Choice**: Stock initiates his talk by highlighting that while having options seems beneficial, it can lead to 'choice overload', making it harder for developers to decide which tools to utilize. **Fragmentation**: The main issue identified is fragmentation within Ruby's developer tools. New developers face numerous decisions, such as installation methods and testing frameworks, unlike more cohesive ecosystems like Rust, which offers a well-integrated experience. **Comparison with Rust**: Stock contrasts the Rust developer experience where tools are developed in coordination with each other, reducing complexity for users. For example, installing Rust is straightforward with a single managed tool, while Ruby offers numerous diverse installation options. **Consequences of Fragmentation**: This fragmentation in Ruby leads to increased learning curves, excessive configuration needs, and makes it difficult for tools to integrate seamlessly. Developers must often relearn tools when switching projects, impeding productivity. **Community Support and Usage Statistics**: The Ruby community has a significantly smaller size compared to JavaScript's, impacting its ability to maintain a wide variety of tools effectively. Furthermore, the lack of adequate tooling for Windows deters a considerable number of potential Ruby developers.