31–40 of 68 posts
Looks like they created mess with AI and then open sourced it. I remembered I had to shift from them to metabase because they closed sourced their deployments docker/kubernetes I guess it was 3 years back. But now AI screwed them over so they come with their own open-source spaghetti.
PostHog has always been open source. I'm not sure why this has been shared on HN at all.
Last time I checked, Posthog self hosted was basically unusable. They have a hobby deployment script which just pulls the latest build from master which varies from “somewhat works” to “completely broken”
[flagged]
Looks like they created mess with AI and then open sourced it. I remembered I had to shift from them to metabase because they closed sourced their deployments docker/kubernetes I guess it was 3 years back. But now AI screwed them over so they come with their own open-source spaghetti.
PostHog has always been open source. I'm not sure why this has been shared on HN at all.
Last time I checked, Posthog self hosted was basically unusable. They have a hobby deployment script which just pulls the latest build from master which varies from “somewhat works” to “completely broken”
Last time I checked, Posthog self hosted was basically unusable. They have a hobby deployment script which just pulls the latest build from master which varies from “somewhat works” to “completely broken”
I just recently switched to posthog self hosted and it works fine
Last time I checked, Posthog self hosted was basically unusable. They have a hobby deployment script which just pulls the latest build from master which varies from “somewhat works” to “completely broken”
In their rationale for this:
> We also learned that the tools to do that automation just don't exist. We kept finding new failure modes. When onboarding a new customer we would have to vet their engineering team for Kubernetes experience so that we'd be confident they could help us debug issues in their PostHog deploy. Folks that didn't have infra experience would often be able to get something set up, only to get stuck when something went wrong.
I empathize that this is a sane choice for PostHog to make as a business. But - if you can't deploy and dogfood your changes, are you truly able to maintain a fork with customizations? And if you can't use your own changes, is the software open-source, or source-available?
Perhaps the punchline is that any scalable & performant web analytics platform must necessarily be a distributed system of ingestion and storage services, and that complexity is like oil and water with the classic "you should be able to swap out the dependencies on your systems with ones you fork" open-source ethos.
PostHog had an opportunity to break this trend, to innovate and invest in those automations they correctly said didn't exist - and I was cheering them on. I've been saddened to see them move in the opposite direction.
Please update title accordingly.
Looks like they created mess with AI and then open sourced it. I remembered I had to shift from them to metabase because they closed sourced their deployments docker/kubernetes I guess it was 3 years back. But now AI screwed them over so they come with their own open-source spaghetti.
PostHog has always been open source. I'm not sure why this has been shared on HN at all.