Ian warns Caleb about making that micro charting library

Ian and Caleb delve into the intricacies of chart libraries and charting frameworks, particularly debating the need for a comprehensive charting library versus a minimal one. Ian believes that a complete library is essential for serious applications while Caleb argues for simplicity and ease of use, leading to a discussion about their personal experiences with libraries like D3, Chart.js, and others.

The conversation pivots to Caleb's plans to build a micro charting library, with Ian expressing concern about the feasibility and the potential limitations of such a library. The two explore the challenges of implementing features like ticks, labels, and different chart types while debating whether a simple solution could suffice for a majority of users. Ian shares skepticism about creating a tool that might end up feeling inadequate as users' needs evolve.

As they discuss user expectations and the necessity for multiple types of charts, Caleb argues for a simplified library that addresses basic needs without overwhelming complexity. Ian counters by asserting that there's often a desire for more sophisticated charts in web applications, advocating for a well-rounded approach that includes a variety of chart options.

The duo engages in a philosophical discussion about the trade-offs between a simplistic UI that fails to meet user demands versus a more feature-rich library that may require users to navigate complex configurations. Caleb expresses a desire to find a middle ground, while Ian stresses the importance of robustness, suggesting that a well-maintained library could elevate user experience.

Towards the end of the conversation, Caleb grapples with the dilemma of whether to continue pursuing his micro charting library project or to integrate existing solutions. They reflect on the importance of striking the right balance between building features users need and avoiding unnecessary complexity that complicates the user experience.