This article sounds like an incoherent rant against CI/CD in general. Coming from Jenkins, App Veyor, Circle CI, and GitLab CI, GH Actions was such a fresh bre

This article sounds like an incoherent rant against CI/CD in general. Coming from Jenkins, App Veyor, Circle CI, and GitLab CI, GH Actions was such a fresh breath and is a very cohesive solution to the cluttered CI space. Most of the "points" mentioned in the article are merely code smells of not using a decent deployment/testing setup. Having centralized build setups is not new either. Ubuntu PPAs and Arch's equivalent of package builds share similar pain points, but it's been serving us for decades at this point.