Skip Navigation

Posts
1
Comments
105
Joined
3 yr. ago

  • I paid for it too!

    It's the first piece of shareware I actually went out of my way to pay for because it was so good that I’d be genuinely pissed off if it died. I'd probably end up switching to pijul or something else for my projects if it ever did.


    I've seen a bunch of people messing the windows version running in linux in the fork forums, so it may be coming in an unsupported capacity.

  • Yeah, I use it when ssh'd into a server, but it's just so awkward to use.

    Sometimes it just really doesn't want to separate a hunk. Other times you want to stage all lines except one, and you have to do a million splits just to target the lines you want to keep.

    It'd be far easier if you could just select the lines you want to affect. It's literally the first feature shown in lazygit's readme. I think half the reason that people use lazygit is that partial commits are so awkward to perform in most other clients.

    Luckily Fork does it as well as lazygit

  • Fork !!!

    It's hands down the best git client.

    It's free as in: sublime text or winzip where they ask you once a month if you want to pay for it but you can just select: I'm still trying it out, and it gets out of your way.

    • It's got a well designed tree graph like in GitKraken except it doesn't lag
    • It's interactive rebasing is as smooth as JJ / LazyGit, so you can edit/rename/reorder your commits except you don't have to have to remember CLI flags since it has its own UI
    • It's lets you commit individual lines by selecting them instead of adding/removing whole hunks like Sourcetree except it isn't filled with paper cuts where a feature breaks in an annoying way for 2 years and you have to do extra steps to keep using it how you want.

    And one killer feature that I haven't seen any other git clients handle: allowing me to stage only one side of the diff. As in: if I change a line (so it shows up as one removed line and one new line in git), I can decide to add the new line change while still keeping the old line.

    So changing this:

     
        
    doThing(1);
    
      

    into this:

     
        
    doThing(2);
    
      

    Shows up in git as:

     
        
    - doThing(1);
    + doThing(2);
    
      

    But if I still want to keep doThing(1);, I don't have to go back into my code to retype doThing(1);, or do any manual copy-pasting. I can just highlight and add only doThing(2); to the staging area and discard the change to doThing(1);.

    So now the code exists as:

     
        
    doThing(1);
    doThing(2);
    
      

    Now with a one-liner example like this, we could always re-enter the code again. But for larger code changes? It's far easier to just highlight the code in the diff and say: yes to this and no to the other stuff.

    And when you get used to it, it makes it really easy to split what would be large git commits into smaller related changes keeping your git history clean and easy to understand.

  • The first problem is they're letting AI touch their code.

    The second problem is they're relying on a human to pick up changes in moved code while using git's built-in diff tools. There's a whole bunch of studies that show how git's diff algorithms are terrible, and how swapping to newer diff algos improves things considerably.

    TL;DR on the studies:

    • Only supporting add/remove/move operations is really bad.
    • Adding syntax awareness to understand if differences in indentation should be brought to a reviewer's attention, improves code and makes code reviews more accurate. (But this is hard because it's language dependent)
    • Adding extra operations (indent/deindent/move/rename-symbol/comment/un-comment/etc...) makes code review easier, faster and more accurate. (But again, most of this requires syntax awareness.


    There's also a bunch of alternative diff algos you can use, but the best ones are paid, and the free ones have fewer features. See:

  • Most new users won't even know that there is a choice until they're presented with it, and most will just stick with the default option anyway. (which most distros have/are switching to wayland)

  • The top comment in the linked article pointed out how that chunk of text was less than truthful:

    There’s definitely regressions that need to be fixed, but the way it is presented here is just misinformation, mixing things like project-specific bugs and misunderstandings in as Wayland problems.

    *BSD is officially supported by Wayland and by several display servers (a better state than for X11 where the *BSD’s had to patch things quite extensively downstream), the graphics tablet thing is a KDE-specific bug, and global hotkeys is available in some display servers through XDG portals (albeit a bit slowly), and using multiple independent mouse cursors is very specifically a Wayland feature (wayland multi-seat). Restoring window state is also supported, it just works differently than X11, and sway at least supports global fullscreen the same way as i3. [...]

    The other comments pick out the other issues the top comment didn't go through.

  • It's worth it for the price.

    General:

    • Explosions / killing / respawning
    • Lots of Star Wars location and sound-design fan service

    Campaign;

    • Gameplay is fun, but simple. The most complicated part is just reading the controls in the settings menu since the game doesn't tell you how to do one of the first things in the first mission (the button you need is 3)
    • Story is basic but it works well as a sequel to Episode 6 and a prequel to The Mandalorian.

    Multiplayer:

    • Take turns being on offence / defence
    • Keep playing the same class / hero character to unlock more abilities for that class / hero character
    • Servers are populated, even for niche locations

    Replayability:

    • Depends
    • If you like regular FPS games, you might get bored of it in 10-20 hours
    • If you like playing the same game over and over again to slowly grind up new things, you'll probably play it for 100+ hours

    Other stuff:

    • Purchase through steam
    • Running the game downloads and installs the EA launcher (but you can log in using your steam account, no need to create new ones)
    • As far as launchers go, the EA launcher is tiny, surprisingly fast, isn't annoying and doesn't get in the way of anything (only setting you'll change is turning off the autolaunch when you start your pc)
    • Achievements work through steam
    • Invite friends through in-game party system. This can only see your friends on the EA launcher, but you can import all your steam friends in the EA launcher in a second and you only have to do it once.
  • It's not about caring, it's about the lawyers making the argument javascript's genericness easier

  • Imagine if god showed up one day and said: "It's actually Jod" then left

  • I was unfamiliar with the decorate flag, but I can't see any difference after trying.

    I will say this is one command I absolutely refuse to create an alias for.

    I have force committed to memory the command: git log --graph --remotes --all (and the variation with the --oneline flag appended to the end if needed) so I can use it anywhere.

    It's the one command I can't live without.

  • The future is webp JPEG XL...

    And telling software patents to burn in hell.

  • It's not AI slop, and we shouldn't need to discuss it.

    But unfortunately some users' behaviour is destructive, so we have to discuss it.

  • There's some really good recommendations in here, but we can't settle on what to recommend for you without a little more info.

    • Are you planning to game on it? (as in computer game, not ttrpg)
      • If yes, use Bazzite. (it's already set up for gaming, and it's "immutable" which means that it'll be hard for you to break)
    • If not, what experience do you prefer more:
      • Windows 7
        • Use Linux Mint (Cinnamon Edition)
      • Windows 10 (but without all the cortana, and bing stuff)
        • Use PopOS
      • I want something Windows like, but I want more control over how I can customise it
        • Use Kubuntu
      • I want something Windows like, and I want more control to customise it, but I also don't want it to break if I start doing weird things to it
        • Use Kionite (Will look the same as Kubuntu from the outside, but will lock you out from doing or using certain things)

    Which one should you pick?

    The answer is No (and also yes).

    Huh?!

    The real answer is not to pick one, but to pick more than one. You can (one at a time) install each of them onto a USB then change your computer's settings to boot up from the USB instead of windows. That way you can try each one to see what you like without installing them on your computer first.

    For each one you try, you can check:

    • Do I like the interface?
    • Are there any compatibility issues? (wifi issues, sound issues, graphics issues, etc...)
    • Am I happy with how long the battery lasts?
    • etc...

    Then once you're ready, you can install the one you want to use onto your laptop.

  • Debian and KDE would make a solid experience, but that's not what this user is looking for.

    They're not going to know what Debian or KDE are, and they're not going to have the requisite knowledge to know that you're probably recommending Kubuntu.

    Kubuntu is a great choice, but since we don't have all the information on the user's needs, it might not be the best choice.

  • I set l to ls -hal

  • A quick and dirty heuristic to find out is to walk through any central transport station or food court and check:

    How many people have customised their phone's lock screen?

  • That's a fairly useless point to make since everyone will always want to look at what configurable options can be adjusted.

    No one would buy a car if they couldn't adjust the seat or mirrors.

  • unrelated, but I love your profile's display pic haha

  • I like the colors, but the sizes of things are pretty inconsistent