3 ms·

The reason people were sounding the alarm 10 years ago is because if you tie yourself to a proprietary platform then you're at its mercy, even if it changes for

• janalsncm 4mo ago
  The comment you are replying to was in response to essentially the same point, albeit with fewer words and less emphasis.
• kibwen 4mo ago
  From the outset, crates.io was careful to deliberately not tie itself inextricably to Github. For example, by resisting the endless deluge of people demanding that Github usernames be used as public-facing package namespaces. Github is only used as an identity provider for logging in.
• arjie 4mo ago
  With open-source projects, realistically there is no shortage of alarm sounding, and there is a shortage of alarm fixing, consequently if you really care about this being fixed you have to volunteer to go fix it.
  • estebank 4mo ago
    Open source projects tend to be (and Rust certainly is) a showupocracy. Shit gets done when people that care about that shit does it. This means that important stuff that everyone agrees is important but not important enough for me to do, doesn't get done. And that some things end up being 80% solutions that scratch the itch of the person driving a project and progress stalls beyond that.
  • a96 4mo ago
    With Github, both of those things are gated behind Microsoft accounts, which will be an absolute no to a lot of volunteers. Particularly the ones who would fix that problem.