4 ms·

- 'one more step away from a corporate-controlled internet" Downvote me to grey-world if you like, but I think everyone's crazy to put all their code infrastru

- 'one more step away from a corporate-controlled internet" Downvote me to grey-world if you like, but I think everyone's crazy to put all their code infrastructure in the hands of fucking Microsoft. Especially literal free open-source software. Who do you think Microsoft is? What do you know of Microsoft's history and their core values (they're "embrace, extinguish & exsanguinate"). It's like giving fucking Sauron safekeeping of your power-rings in Mordor, oh we have great infrastructure for safe ring storage here, very secure, the orcs are really expert guards.

rsuelzer 3y ago
But, I like the stock.
- layer8 3y ago
  Now imagine having your shares managed by a Microsoft bank — maybe in SharePoint. ;)
  - lanstein 3y ago
    We can help find them
  - tanseydavid 3y ago
    They could call it "Microsoft Money" -- oh wait, that's been used already and is now in the graveyard. ps. Sharepoint <shudder>
BHSPitMonkey 3y ago
What exactly is the risk? That they'll stop providing the services they sell today? The design of git makes switching to another primary remote very easy (granted, most users probably don't have good habits around backing up data from Issues/Wiki/Releases and risk losing that data if it's taken away suddenly -- but the repo itself is durable and portable on a whim.
- eviks 3y ago
  > (granted, most users probably don't have good habits around backing up data from Issues/Wiki/Releases and risk losing that data if it's taken away suddenly so it's actually very hard to switch
  - cco 3y ago
    Given how common defaulting on issues is, many maintainers might view this as a feature? Only slightly kidding.
    - Tommah 3y ago
      At one of my jobs, they used Asana when I started. It was too full of backlogged issues, so we moved over to Jira. Then Jira got too full. A month before I was laid off, one of my coworkers said, "Maybe we should try out Asana."
- bguebert 3y ago
  I think the risk is the extensions that github adds to git like CI/CD and issue tracking features.
- Klonoar 3y ago
  You have slightly illustrated it yourself in a roundabout way, but let's be clear with wording here: > The design of git makes switching to another primary remote very easy It is never as easy as just switching to another primary remote. It's not just Issues/Wikis/Releases, but the build/CI process(es) that are rampant on GitHub now, the community you've built potentially coming up on GitHub and not really getting that there's anything else out there, etc. This is all time consuming hard work. People will often just not do it, and this is why we have lock in everywhere. Stop calling it easy. The centralization of the internet around a few specific services - like GitHub, Cloudflare, and so on - is an increasingly problematic thing to contend with. Edit: "as a easy" -> "as easy"
  - dboreham 3y ago

rsuelzer 3y ago

But, I like the stock.

layer8 3y ago
Now imagine having your shares managed by a Microsoft bank — maybe in SharePoint. ;)
- lanstein 3y ago
  We can help find them
- tanseydavid 3y ago
  They could call it "Microsoft Money" -- oh wait, that's been used already and is now in the graveyard. ps. Sharepoint <shudder>

BHSPitMonkey 3y ago

What exactly is the risk? That they'll stop providing the services they sell today? The design of git makes switching to another primary remote very easy (granted, most users probably don't have good habits around backing up data from Issues/Wiki/Releases and risk losing that data if it's taken away suddenly -- but the repo itself is durable and portable on a whim.

eviks 3y ago
> (granted, most users probably don't have good habits around backing up data from Issues/Wiki/Releases and risk losing that data if it's taken away suddenly so it's actually very hard to switch
- cco 3y ago
  Given how common defaulting on issues is, many maintainers might view this as a feature? Only slightly kidding.
  - Tommah 3y ago
    At one of my jobs, they used Asana when I started. It was too full of backlogged issues, so we moved over to Jira. Then Jira got too full. A month before I was laid off, one of my coworkers said, "Maybe we should try out Asana."
bguebert 3y ago
I think the risk is the extensions that github adds to git like CI/CD and issue tracking features.
Klonoar 3y ago
You have slightly illustrated it yourself in a roundabout way, but let's be clear with wording here: > The design of git makes switching to another primary remote very easy It is never as easy as just switching to another primary remote. It's not just Issues/Wikis/Releases, but the build/CI process(es) that are rampant on GitHub now, the community you've built potentially coming up on GitHub and not really getting that there's anything else out there, etc. This is all time consuming hard work. People will often just not do it, and this is why we have lock in everywhere. Stop calling it easy. The centralization of the internet around a few specific services - like GitHub, Cloudflare, and so on - is an increasingly problematic thing to contend with. Edit: "as a easy" -> "as easy"
- dboreham 3y ago