Post #1201238

2026-04-01 03:50 UTC

@ironicbadger Could anyone explain to me, how is this possible? I would imagine they would keep things running on the original hardware etc. which I wouldn't expect to fluctuate like this.

Replies (5)

@mgedmin@floss.social 2026-04-01 04:24

@Jourei @ironicbadger Move fast and break things!

Open ##1201239
@hikhvar@norden.social 2026-04-01 05:43

@Jourei AFAIK they started to use Azure more and more. That would explain the initial stability after the buy event. Also they might have shifted from stability to ship feature after feature. Before Microsoft bought them, their feature set was rather stable. @ironicbadger

Open ##1201240
@muan@mastodon.social 2026-04-01 05:47

@Jourei @ironicbadger No, when MSFT came in they tried to change everything at once. If anything services fee can be paid back into MSFT pipelines instead of other service providers, they wanted it yesterday. They brought in more than 1000 people, which was more than all of GitHub at the time, to dilute the original teams.

Open ##1201241
@crazyeddie@mastodon.social 2026-04-01 06:24

@Jourei @ironicbadger "restructuring" They fired huge chunks of the existing staff and terrified the rest.

Open ##1201242
@deef@trg.social 2026-04-02 00:27

@Jourei @ironicbadger Yeah, this is likely just a bad graph. Before vs after the change was likely a change in either the definition of, or the measuring of "down time", and the two end up not comparable. I suspect the data went from tracking as "most/key things working=up" to "anything not working=not up"

Open ##1201245