I found out when Actions started failing again for the Nth time this month.

The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.

▲

hinkley 2 days ago | parent | next [-]

If you consider that an American maintainer was cheesed off enough to move an entire project off GitHub two days before Thanksgiving then the tone of the original post was completely in line with the energy involved.

Anger is a communication tool. It should absolutely be used when boundaries are being violated. Otherwise you’ll get walked all over.

▲

bilkow 2 days ago | parent [-]

I mostly agree, but a generalized attack at the remaining GitHub workers by calling them "losers" and then "rookies" is unwarranted and leaves a bad taste IMO.

See the edit history here: https://news.ycombinator.com/item?id=46133179

Edit: 1. just to be clear, it's very good that they have accepted the feedback and removed that part, but there's no apology (as far as I know) and it still makes you wonder about the culture. On the other side, people make mistakes under stress. 2. /s/not warranted/unwarranted/

	▲	Nextgrid a day ago \| parent [-]
		A structural engineer will not sign off on bad designs no matter how much pressure the company applies to them. They will resign and/or report the incident to their local regulator as a safety issue. We don't have that for developers. Maybe shame/offense is our next best bet. You are free to work for a terrible company accepting and/or encouraging terrible design decisions, but you need to take into account the potential of being laughed at for said decisions.

▲

IgorPartola 2 days ago | parent | prev | next [-]

The Zig post has since been updated and the objectionable parts have been removed. I think we can put that part to rest.

▲

landr0id 2 days ago | parent [-]

I have no problem with their opinions but I don’t think it should have been said in a Foundation post.

It may have been updated, but nobody is reading the update.

	▲	000ooo000 2 days ago \| parent \| next [-]
		OK, so we keep banging on about it forever? Move on
	▲	esseph 2 days ago \| parent \| prev [-]
		I just did and wouldn't have know about it if it hadn't been talked about here.

▲

YetAnotherNick 2 days ago | parent | prev | next [-]

Idk, if being bad is the reason for leaving Github Actions, I think people would have left it ages ago. It stuck not because it is better than competitors but because it is included in the Github plans. It's decaying implies that it has somehow became worse, in fact it was one of the worst implementation to start with.

▲

stefan_ 2 days ago | parent | prev | next [-]

GitHub has seem to come under the same management as VSCode, everything has to be made AI and that is the only priority. It's like the Google+ of old but stupider.

	▲	chrisandchris 2 days ago \| parent [-]
		Hopefully with that much AI they can finally make the Explore page more useful than "most stars" and "most recent updated". There seems to be no way to discover stuff on GitHub except knowing where it is (hence not discovering but knowing).

▲

2 days ago | parent | prev | next [-]

[deleted]

▲

DetroitThrow 2 days ago | parent | prev | next [-]

Combined with security concerns, this made us reconsider even our self-hosted GH Actions last month.

GH Packages is something we're extricating ourselves from after today too. One more outage in the next year and maybe we get the ammunition to move away from GH entirely.

It's still hard to believe that they couldn't even keep the lights on on this thing.

▲

zenlot 2 days ago | parent | prev [-]

[dead]