>>jcalab+(OP)
See also this thread: https://news.ycombinator.com/item?id=35967797 which just came up about GitHub stability sentiment.

>>jcalab+(OP)
Again? Last time this happened was 5 days ago. [0]

It is not even the end of the month and the outages are increasing every month and it is now chronically unreliable. Seriously, we have given GitHub more than 3 years to improve and it clearly isn't working. That is plenty of time.

At this point, you might as well self-host like the rest of the open source projects out there, since GitHub is falling apart every week and it seems to be more reliable to self-host than to sit on GitHub, go all in and tolerate these outages every calendar month.

[0] https://news.ycombinator.com/item?id=35903116

>>jcalab+(OP)
They Just published this blog post https://github.blog/2023-05-16-addressing-githubs-recent-ava...

>>mulmen+E5
Yeah but transition is not fully required until September 1, 2023 [1]

[1] https://news.ycombinator.com/item?id=34773860

>>gianca+q6
Skype was also horribly insecure and leaked your IP which was a cause of a lot of folks in esports getting DDoS'd from it[0].

0: https://blog.destiny.gg/protection-from-ddos-attacks/

>>mulmen+16
BTW: There is work in progress to decentralize modern git based workflows by https://nlnet.nl/project/ForgeFed/ (paid for by the European Union), by decentralizing git not at the client level (which it obv. already has, but most people only use one origin), but also on the code forge level.

>>exogen+O5
I keep a rolling Twitter thread with all the UI bugs I notice: https://twitter.com/underyx/status/1600943582760042497

>>teduna+jm
No, in general almost never in tech, only rarely and when unionized or when protected by contract or labor law. And we're not talking about seasonal jobs (logging, fishing) either. And we're not talking about unforeseen circumstances/force majeure like in 2020/1.

"RIF" is US jargon; you can see that ~0% of worldwide Google usage outside of North America for "RIF" is "reduction in force" [https://trends.google.com/trends/explore?date=now%201-d&q=%2...]. A tiny amount (<<2%) of usage in UK, Scandinavia, Poland, Australia (possibly mainly from US multinationals).

More corroboration: https://en.wikipedia.org/wiki/RIF

There is zero reason to adopt managementspeak jargon, or its 2022 neologisms "impacted"/"affected"/"displaced". Just say "layoff" (n) / "laid off" (v), already.

In the very unlikely event [in tech] you actually needed to say "temporary layoff", you can easily say "temporary layoff".

The language was working fine for decades and there's no reason to pander to management euphemisms. It harms clarity.