Live data from Hacker News

I regret migrating to Codeberg

xn--gckvb8fzb.com

101–110 of 617 posts

Re: I regret migrating to Codeberg

#101

Earlier quoted context omitted.

[flagged]

You are American? American non profit associations must have officers and a board of directors.

I am, and I'm sure there are rules for non-profits in the US that are just as tedious! Like I said in a different comment, I didn't realize Codeberg had a whole German non-profit thing behind it.

Re: I regret migrating to Codeberg

#105
The answer to big platforms enshittifying is not to move to smaller versions of the same thing. This didn't work for GitHub -> Codeberg/Sourcehut, it didn't work for Twitter -> Mastodon. Because the problem is not necessarily the size, it's the power. Codeberg is exerting power beyond what it should and users have little recourse and get caught up in the issues, some Mastodon servers are fine but there have been plenty of admins who had the power go to their heads or had fallings out with other parts of the network, and again it's the users who get caught up in it.

The answer is building systems that prevent that power trip from ever happening. This is why Bluesky is a better answer to Twitter than Mastodon – the company has its faults, but the approach is a fundamental step forward that Mastodon did not take. The same thing is true of things like Tangled for a software forge. It's no surprise that both of these are based on ATProto, although I'm not saying ATProto is the only option here.

Re: I regret migrating to Codeberg

#106

The author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects. I don't share that concern. It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources. Personally, I have a group of friends who share a GitLab instance, for example.…

I do think the author is right that the Codeberg post was wrong to assert that "community" is a measure of the legitimacy of a FOSS project A massive amount of technology runs on essentially single-contributor projects with pretty much no "community": xz, core-js, GnuPG, NTPd, OpenSSL, cURL They didn't need to make that implication or alienate solo devs in order to drive home their point

Uh, I thunk you’re underestimating the community around most of those. BDFL doesn’t mean single-contributor.

Re: I regret migrating to Codeberg

#107

I wonder how anyone can migrate to codeberg. Every time I check, the site is lagging. Few days ago I registered and tried to create a repository. I couldn't, site busy or something. The migration towards codeberg already started a while ago, don't see how it can scale.

Perhaps they started banning entire categories of projects so their infra could actually work again.

Banning a portion of their community is... one way to reduce server load.

Re: I regret migrating to Codeberg

#108
I think Codeberg is well within its rights to offer services in the way that it wants. If customers don't like it they can move & stop paying. Find a host that fits the terms you want and expect. That is what is great about Codeberg, no lockin no scam.

Re: I regret migrating to Codeberg

#109

The answer to big platforms enshittifying is not to move to smaller versions of the same thing. This didn't work for GitHub -> Codeberg/Sourcehut, it didn't work for Twitter -> Mastodon. Because the problem is not necessarily the size, it's the power. Codeberg is exerting power beyond what it should and users have little recourse and get caught up in the issues, some Mastodon servers are fine but there have been plen…

How does Bluesky or ATProto prevent that power trip?

Re: I regret migrating to Codeberg

#110
post #47

Earlier quoted context omitted.

So I voted against, partly because I feel that the text doesn't to justice to such a multifaceted topic. If all projects on Codeberg were human-written, that would be a big seal of quality! There are a lot of projects coming out now where someone feels like they've made a cool thing but it breaks on the first edge case and is entirely unmaintainable. Many are built on wrong principles because the prompt authors aren'…

A big seal of quality because it is human written? Maybe in narrow spaces but in general, I’d put money on the average developer being significantly worse at writing code with bugs than an AI. It’s codebergs infra so their choice, but it seems like an overly simplistic solution to a complicated advancing technology, in that it is a threadbare line between “vibe-coded” and “complex agent harness with human oversight a…

I’d put money on the average developer being significantly worse at writing code with bugs than an AI.

I'd take that bet if it was measured in "bugs per day" instead of "bugs per LOC". LLMs generate far fewer bugs in absolute terms, but they also generate far more code, so it probably balances out if everything is equal. I think LLMs will actually lead to more bugs just because they're usually working with poorly defined requirements (prompts) and they guess to fill in the gaps based on the averages of their training data. A lot of those guesses are wrong.

Where LLMs win though is the severity. An LLM will write buggy code in the sense that it doesn't do what you wanted it, but not so much in the sense of security or data loss bugs. They get that right more than humans because they're trained to care about that stuff. There's far more "how to write good code" content in the training data than "how to not care about security and go fast" content (because writing that would be weird!)

Post reply on HN