<story><title>Weaveworks is shutting down</title><url>https://www.linkedin.com/posts/richardsonalexis_hi-everyone-i-am-very-sad-to-announce-activity-7160295096825860096-ZS67</url></story><parent_chain><item><author>marcinzm</author><text>&amp;gt; Also it really feels like all the air has been let out of the docker&amp;#x2F;kubernetes&amp;#x2F;cloud-native balloon that was so popular in the late 2010s.&lt;p&gt;Not really, the space has simply grown faster than these companies could keep up with and were left behind.&lt;p&gt;I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local testing. That wasn&amp;#x27;t the case 5 years ago but it is now. Why would I want to be locked into Weave Works?</text></item><item><author>mad_vill</author><text>I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main  revenue driver is consultancy.&lt;p&gt;Also it really feels like all the air has been let out of the docker&amp;#x2F;kubernetes&amp;#x2F;cloud-native balloon that was so popular in the late 2010s.</text></item></parent_chain><comment><author>benjaminwootton</author><text>GitHub actions must have eaten most of the DevOps tooling market.  It’s pretty good and it’s fine for the vast majority of pipelines.</text></comment>
<story><title>Weaveworks is shutting down</title><url>https://www.linkedin.com/posts/richardsonalexis_hi-everyone-i-am-very-sad-to-announce-activity-7160295096825860096-ZS67</url></story><parent_chain><item><author>marcinzm</author><text>&amp;gt; Also it really feels like all the air has been let out of the docker&amp;#x2F;kubernetes&amp;#x2F;cloud-native balloon that was so popular in the late 2010s.&lt;p&gt;Not really, the space has simply grown faster than these companies could keep up with and were left behind.&lt;p&gt;I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local testing. That wasn&amp;#x27;t the case 5 years ago but it is now. Why would I want to be locked into Weave Works?</text></item><item><author>mad_vill</author><text>I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main  revenue driver is consultancy.&lt;p&gt;Also it really feels like all the air has been let out of the docker&amp;#x2F;kubernetes&amp;#x2F;cloud-native balloon that was so popular in the late 2010s.</text></item></parent_chain><comment><author>xenophonf</author><text>&amp;gt; &lt;i&gt;a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions... [with] docker compose for local testing&lt;/i&gt;&lt;p&gt;Please teach me, oh wise prince!</text></comment>