Are you guys fine with these new shenanigans from Github. I found a bug and wanted to check what has been the development on that, only to find out most of the discussion was hidden by github and requesting me to sign-in to view it.

It threw me straight back to when Microsoft acquired Github and the discussions around the future of opensource on a microsoft owned infrastructure, now microsoft is exploiting free work from the community to train its AI, and building walls around its product, are open source contributors fine with that ?

  • @[email protected]
    link
    fedilink
    87 months ago

    The biggest issue with gitlab is the web editor. They swapped out a really fast and light-feeling one for this frankenstein monster that looks like whatever the hell the barbies and kens writing powershell are using. It’s so slow, and so ugly.

    Everything else about gitlab, so far, has been great. From v9 to here, it’s been easy to use and easy to upgrade; but we can debate the capricious worsening of the sidebar for something surprisingly worse each time .

    • @[email protected]
      link
      fedilink
      27 months ago

      Who even uses the web editor on any git website though? For anything besides micro fixes for projects I don’t already have cloned, I find it easier to just update things locally and push.

      Don’t even get me started on github rendering tabs as EIGHT spaces.

      • @[email protected]
        link
        fedilink
        17 months ago

        A lot of people do. Especially on GitHub, where you can just browse a random repository, find a file you want to change, hit the edit button, and edit it right there in the browser (it does the forking for you behind the scenes). For people unfamiliar with git, that’s huge.

        It’s also a great boon when you don’t want to clone the repo locally! For example, when I’m on a slow, metered connection, I have no desire to spend 10+ minutes (and half of my data cap) for a repo to clone, just so I can fix a typo. With the web editor, I can accomplish the same thing with very little network traffic, in about 1 minute.

        While normally I prefer the comfort of my Emacs, there are situations where a workflow that happens entirely in the browser is simply more practical.