Why I Prefer Hosting My Code Elsewhere: A Developer’s Perspective

In summary, while acknowledging some benefits of git forges like increased transparency and potential community engagement, the author remains hesitant to switch from their current approach due to concerns surrounding loss of control over code ownership (especially with non-free software), privacy issues related to account creation, centralization risks associated with monoculture platforms such as Github (now Microsoft owned), additional effort required for migration without guaranteeing desired improvements, and lack of a perfect alternative combining the advantages of both systems. They express interest in exploring solutions that combine public discussion with private communication options while maintaining security measures and configurable workflows within lightweight software frameworks.

However, they emphasize their openness to further discussions on potential ways to achieve this balance between traditional methods and modern collaboration tools without compromising core principles.

Complete Article after the Jump: Here!