Live data from Hacker News

Weaveworks is shutting down

linkedin.com

181–190 of 266 posts

Re: Weaveworks is shutting down

#181
post #158
post #128

Earlier quoted context omitted.

> Something is clearly better than nothing. To you and I, this is patently obvious. This is not true however for VCs. In a lot of them, they'd prefer you fail entirely rather than limp along making 1x, 1.5x their investment. Zeroing out is preferable sometimes, weirdly.

Do you have any sense why this is true? I get preferring (10x or 0x) to (1.5x). I don’t get preferring a near-certainty of 0x to some recovery of their capital with a pivot to selling a smaller-but-sustainable business. Is it something like they’re measured by LP’s (or someone?) on only non-zeroed investments?

[deleted]

Re: Weaveworks is shutting down

#182
post #73
post #64

Earlier quoted context omitted.

Atlassian’s market cap is $55 billion. GitLab’s market cap is $11 billion. GitHub sold for $7.5 billion in 2018. There’s money, you just have to be more than a point solution.

Atlassian is way more than dev tooling at this point and GitHub's user count is insane.

[dead]

Re: Weaveworks is shutting down

#183
post #119

Earlier quoted context omitted.

"Shoot for the moon" seems like a reasonable strategy when you're making the investment. However, certainly at some point while they were burning through that $36 million it became evident that "moon" was no longer a viable destination. Why wouldn't everyone be aligned with making the adjustments needed to get back to default alive? Something is clearly better than nothing. Now if it got to the stage where the CEO no…

Because this is not what the VC wants. The VCs are diversified across many startups and frankly make most of their money from tail event startups in their portfolio (e.g. Uber / Facebook). Since they don't know which startup will be the tail event, they don't want a profitable business, but a max growing business. This is different from the bootstrap model.

[deleted]

Re: Weaveworks is shutting down

#184
It’s a pretty awful note.

“ The company was turning over double digit (>$10M) revenue and had more than doubled the number of new product logos in 2023.”

Sounds like he was measuring the wrong things.

“I could say that this should not have happened, but I know that we are not alone in this market.”

Sounds like he’s justifying his failure by point at others in the market.

Written like a Wall Street trader. Oh wait…

Re: Weaveworks is shutting down

#185
post #90

Flux for me was always superior to ArgoCD from a technical point of view, but they over the years ArgoCD became the more popular tool. I wonder if it was marketing, the missing UI or something else? But super sad to see weaveworks shutting down I hope that the open source projects will continue to evolve.

I guess it was UI, indeed. Whatever "true engineers" think or say, it is an attractive option for many potential users (think not of Ops only, but of Devs, too). Therefore, it brings a bigger audience, i.e. more adopters, more contributors, more integrations, more whatever…

Re: Weaveworks is shutting down

#187

I think it's worth giving praise for their contributions to Flux. In my network, I'm the only one using ArgoCD. Supposedly they're equals, but it always made me curious to try Flux. Are there any statements about the future of Flux and other open source tools, and whether the remaining community has enough resources to maintain development, or if they will reduce their contributions to only fixing critical bugs?

Can't tell for all their projects, but Flux seems to be safe. Stefan Prodan joined ControlPlane last month already and keeps developing Flux CD. Its latest release (v2.2.3) was delivered while working in the new company. He is also working on Enterprise Distribution for Flux CD (https://github.com/controlplaneio-fluxcd/distribution) there now.

Re: Weaveworks is shutting down

#188

Earlier quoted context omitted.

> 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 Please teach me, oh wise prince!

“it’s that easy!”

I'd love to see 7K of YAML as every time I've asked, no one's been able to show me a fully worked, end-to-end example.

Re: Weaveworks is shutting down

#189
post #90

Flux for me was always superior to ArgoCD from a technical point of view, but they over the years ArgoCD became the more popular tool. I wonder if it was marketing, the missing UI or something else? But super sad to see weaveworks shutting down I hope that the open source projects will continue to evolve.

Better UI

I personally consider the ArgoCD UI an anti-feature. Attaching some hulking mass of Javascript dependencies to the thing that has cluster-admin rights to my production cluster is unnecessary attack surface for me.

ArgoCD also has its own auth system and permissions. You give ArgoCD cluster-admin rights, then it uses impersonation to pretend like it has lower permissions. One little bug there and you can trick ArgoCD into escalating your permissions, which happens a lot: https://github.com/argoproj/argo-cd/security/advisories/GHSA...

While not officially supported, you can technically deploy Flux with limited permissions, but ArgoCD's dependence on impersonation means it cannot run with lower permissions.

Re: Weaveworks is shutting down

#190
post #126
post #119

Earlier quoted context omitted.

"Shoot for the moon" seems like a reasonable strategy when you're making the investment. However, certainly at some point while they were burning through that $36 million it became evident that "moon" was no longer a viable destination. Why wouldn't everyone be aligned with making the adjustments needed to get back to default alive? Something is clearly better than nothing. Now if it got to the stage where the CEO no…

> Something is clearly better than nothing. That's not a major component of venture backed startups. For a company that has already been written off as a failure, often the board members that represent the VC would rather not have to stay involved and keep showing up for meetings -- they could be elsewhere; there's an opportunity cost.

It's not like a board seat is this magic item that is stuck to you and you can't get rid of of you tried.

If a VC had truly written off the company, and board meetings are not worth their time anymore, they can just resign their seat.

Post reply on HN