Summary:
GitHub is increasingly using React to build new features, aiming for a more app-like experience.
This shift is driven by the need to compete with modern competitors and improve mobile usability.
The decision contrasts with some opinions favoring simpler JavaScript approaches, showcasing the challenges of large-scale platform updates.
The future of Azure DevOps is uncertain, with Microsoft's desire to eventually migrate users to GitHub.
The community debates the merits of app-like designs for developer tools, raising questions about feature bloat and mobile priorities.
GitHub's UI Transformation: Embracing React for a More App-Like Experience
<img src="https://devclass.com/wp-content/uploads/2018/08/shutterstock_389742523-768x427.jpg" alt="GitHub UI" title="GitHub UI">A GitHub software engineer recently revealed the platform's UI evolution, highlighting a significant shift towards React. Driven by the need for a more dynamic and app-like experience, GitHub is increasingly adopting React for new features. This move aims to compete with modern, app-like competitors and better serve users on mobile devices.
The Current State of GitHub's UI
GitHub, a Ruby on Rails monolith, boasts a massive codebase. With thousands of models, routes, and controllers, and hundreds of developers contributing monthly, maintaining and improving the UI is a significant undertaking.
Why React?
The decision to embrace React is primarily driven by the desire to create a more dynamic UI, particularly for mobile users. While a complete rewrite isn't planned, new features are increasingly being built using React, leveraging the Primer Design System's support for React components.
This decision contrasts somewhat with the opinions of some developers, notably David Heinemeier Hansson (creator of Rails), who advocates for avoiding JavaScript frameworks requiring build steps. However, the scale and complexity of GitHub's platform may warrant a different approach.
The Future of Azure DevOps
Interestingly, Microsoft's acquisition of GitHub included a desire to eventually migrate users from Azure DevOps to GitHub. While both platforms currently coexist, GitHub's faster development pace suggests a brighter future for the platform. The discussion highlights existing feature gaps between the two, such as the more mature Azure Test Plans compared to GitHub's offerings.
Community Debate
The move towards a more app-like experience using React has generated mixed reactions within the developer community. Some praise the improvements, while others express concerns about feature bloat and usability, particularly concerning the mobile experience.
Key Takeaways
GitHub's journey underscores the challenges of balancing legacy systems with modern development practices. The adoption of React highlights the growing need for dynamic and app-like interfaces, especially in the context of mobile development and competition. The long-term implications of this choice, and its impact on the relationship with Azure DevOps, remain an interesting storyline to follow.
Comments
Join Our Community
Create an account to share your thoughts, engage with others, and be part of our growing community.