• 1 Post
  • 94 Comments
Joined 2 years ago
cake
Cake day: August 30th, 2024

help-circle

  • A lot of people are against it because they see it as the first step towards evil, but I still think we should have some sort of recommendation algorithm. New content discovery on Lemmy is way too manual for normies like me.

    The sign-up process should be streamlined. It’s really intimidating to have to choose an instance when you don’t even understand what the heck that is. And then there’s the manual account validation. I’m not sure what the solution is but we might want to find one.

    And we need to do something about the extremists. They have a right to exist, but the abnormally high prevalence of American-coded communist/anarcho-communist content that just casually talks about executing the rich and the like is weird and intimidating even to me, a decidedly left-wing person. Americans, who are famously doubtful of communism, probably run away from the platform seeing that. And as for non-Americans… Well the proportion of content that’s specifically about American politics is even higher than on Reddit, which is saying something.








  • Huh. Never thought of it that way. I was never bothered by a long commit history at all. Search and filter tools in the git client always get me where I want.

    The one issue I have is when there are way too many extant branches and the graph takes up happy half my screen.

    But that’s more of a Fork issue than it is a fundamental one. The Fork dev could conceivably find a solution for that.

    Either way, I guess I see what you mean. I’m just not that strict about commits. Commits just for the linter aren’t a thing since we have a pre-commit hook for that, and typo-fixing commits… Well, they happen, but they’re typically not numerous enough that I’d find them to be any sort of issue.

    As for whether I’d really want to revert a particular change – while I work, yes. Afterwards, I see what you mean; i could probably squash 50 commits into 15 or something. But when I think about the time investment of reviewing every commit and thinking about how they ought to be grouped together before making my merge request… I have a lot of trouble convincing myself it’s a good time investment.

    Maybe I’d think otherwise if we had a huge team. We have maybe 10 devs on this project at any given time.


  • That’s a good explanation of what it’s supposed to do. That was how I understood it as well.

    But anytime I’ve tried it, I’ve ended up with conflicts where there shouldn’t be (like, I already solved that conflict when I merged earlier) and/or completely undesirable results in the end (for instance, some of my changes are just NOT in the result).

    So I just gave up on the whole feature. Simpler to just merge the source branch into mine.