Onedev is pretty good. I run it locally and it’s been grwat
Also there is just something about its sidebar-centric UI I just don't like. It's not as bad as gitlab but still, it bugs me every time I use it.
71–80 of 138 posts
Onedev is pretty good. I run it locally and it’s been grwat
Also there is just something about its sidebar-centric UI I just don't like. It's not as bad as gitlab but still, it bugs me every time I use it.
Earlier quoted context omitted.
You and the parent seem to dislike the author sharing their opinions on things on their own blog . And yet you're happy to share your own dismissive opinions on the author here. FWIW I find the author's obviously subjective opinions on their tools much more valuable than your obviously subjective opinions of this author.
They’re not saying that the author can’t post whatever they want on their blog. They’re saying that we, as a community, should not elevate unsubstantiated writing that comes across as “I don’t truly understand these things or have deep experience, but this is what everyone else says on every other blog post or comment, and I’m parroting it”. I would add on to it that I feel there’s sometimes a real thing in these dis…
Kubernetes is a nightmare, and I'm glad that some people are not afraid to point out the state of the emperor's outfit.
Earlier quoted context omitted.
SourceHut staff here. We don't have any requirement for "real legal" names or anything -- and in fact I find these requirements very harmful in general (glad we finally got rid of them in the kernel). I know multiple people collaborating on SourceHut with a pseudonym and this causes no issue at all. SourceHut does assume a stable email address but that's about it. That's my own take -- for Drew's see https://drewdeva…
It's not a requirement, but I heavily got the vibe that pseudonyms are not welcome. To quote Drew, "You should be using your real email address with the mailing lists, so that people can reach you and treat you as a human being, not as a proxy of one." I'm just not comfortable putting myself out there like that. I get it's not technically against the rules to do it differently, but it's just... frowned upon. Other ju…
> I hope they haven’t started down the slow and painful process of enshittification by following vague, ill-defined industry trends! Has anyone else found themselves wondering if GitHub switched to a different web framework? I feel like they moved further down the client-side rendering rabbit hole recently. Their UI feels increasingly janky to me. Several times a day I get a view of completely un-styled HTML that eve…
Having tried GitHub, GitLab, Source Hut, Codeberg, and BitBucket (RIP), I think the only serious options are GitHub, GitLab self hosted, and Source Hut. GitHub owned by MSFT aside, and also putting their AI push _also_ aside, GitHub has things like Sponsors, Dependabot, and code scanning that you won't find anywhere else. They sure are luring you into ecosystems that require a huge escape velocity, but GitHub serves…
I was hoping for an evaluation of Radicle--the only forge that seemed to be doing something exciting and "new", and one I haven't had the time to really analyze yet--but... no such luck :(.
https://pierre.co/ is another interesting one, focused on a product-development workflow.
This post bothered me. Perhaps I'm being too nitpicky, and there's nothing inherently wrong with their final choices, but their criticisms of the other systems alongside their reasons for choosing what they did are contradictory; overall the article was internally inconsistent. Gitlab was dismissed for the SaaS being only open-core, despite opting for self-hosting in the end. Codeberg was dismissed for having limited…
Yet they ended up choosing a self-hosted option, Gitea, because it was recommended by an acquaintance and they set up a couple lightsail servers on AWS to run it.
It's totally fine for the author to share their preferences; they're just exhibiting the internal inconsistencies and irrational behavior we're probably all guilty of at one point or another.
This post bothered me. Perhaps I'm being too nitpicky, and there's nothing inherently wrong with their final choices, but their criticisms of the other systems alongside their reasons for choosing what they did are contradictory; overall the article was internally inconsistent. Gitlab was dismissed for the SaaS being only open-core, despite opting for self-hosting in the end. Codeberg was dismissed for having limited…
Open-core was mentioned, but was not a dealbreaker. Gitlab was dismissed for just following along with what GitHub does and being "AI-powered"
Earlier quoted context omitted.
https://pierre.co/ is another interesting one, focused on a product-development workflow.
What is a Product Engineer? Is it just another name for an engineer?
Today in software companies there is basically a gap where each discipline kinda prefers to work in it's own software silo (eg. Asana / Figma / GitHub), but that doesn't really make a lot of sense from a fundamental standpoint where all of those aspects of a team want to work very closely together. You end up kinda syncing a lot of info/state across the silos, or via meetingss/slack etc, so I think Pierre is trying to bring all that into one tool with some opinionated workflow. Makes a lot of sense from my perspective, curious how it ends up working out.