• 0 Posts
  • 15 Comments
Joined 4 months ago
cake
Cake day: March 4th, 2024

help-circle

  • Up to 2.x, GNOME used what was basically the MacOS philosophy: make things easy and simple and intuitive, but if the user wants finer control and power features, make sure it’s still possible somehow. GNOME 3 and later pretty much adopted the philosophy that there’s the GNOME path of simplicity and streamlining, and power user functionality is going to be removed from the core and relegated to extensions. And, of course, GNOME started requiring boatloads of memory to run, which to me didn’t go hand in hand with “simplicity”.

    I eventually settled on using XFCE, because it didn’t have the bloat and still had enough customisability. Really good environment for old and underperforming systems. If I’m using a modern high performance system, I’m actually pretty impressed by what KDE Plasma is doing these days.





  • When I was learning about GIMP key shortcuts I was like “Ctrl+A selects everything, Ctrl+Shift+A deselects everything. Makes sense.”

    And then I went to most of the other apps. “Ctrl+D? Well it’s one less keypress, but… WHY?”

    To be fair, I get it now, I’ve used plenty of image editors and I remember the keybinds wherever I am. Just that I sometimes find it annoying that The Other Software hasn’t adopted logical keybindings.

    (I find it particularly annoying that a lot of image editors try to be fancy and sophisticated and Photoshop-compatible and think it’s at all appropriate to use Ctrl+NumpadPlus and Ctrl+NumpadMinus for zooming. Just use what GIMP uses! NumpadPlus and NumpadMinus. It’s not hard! What are you using the plain plus and minus for, anyway? Absolutely nothing! I just checked, I need to use Ctrl in Affinity Photo. Plain plus and minus are useless. I see you. …oh I can just rebind these. Done.)


  • I’ve been using GIMP since the very dawn, I use plenty of other image editors for variety of reasons (Affinity Photo, DxO PhotoLab, ArtRage, Clip Studio), and I have no problems with the UIs in any of them.

    Yet every time I use Adobe software I’m like “why is it doing this? Why is it designed this way? Who thought that was a good idea? This is stupid.”


  • Actually this reminds me, what is the deal with tar command recommendations to use or not use dash? I know GNU tar accepts both (e.g.) tar xvf file.tar and tar -xvf file.tar, but at some points people were like “NO! Don’t use the dash! It’s going to maybe cause issues somewhere, who knows!” and I was like “OK”. Something to do with people up designing the Unix specs?


  • About 10 years ago I was like “FINE, clearly 512MB of memory isn’t enough to avoid swapping hell, I’ll get 1 GB of extra memory.” …and that was that!

    These days I’m like “4 GB on a single board computer? Oh that’s fine. You may need that much to run a browser. And who’s going to run a browser regularly on a SBC? …oh I’ve done it a lot of times and it’s… fine.”

    The thing I learned is that you can run a whole bunch of SHIT HOT server software on a system with less than a gigabyte of memory. The moment you run a web browser? FUCK ALL THAT.

    And that’s basically what I found out long ago. I had a laptop that had like 32 megs of memory. Could be a perfectly productive person with that. Emacs. Darcs. SSH over a weird USB Wi-Fi dongle. But running a web browser? Can’t do Firefox. Opera kinda worked. Wouldn’t work nowadays, no. But Emacs probably still would.




  • Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.


  • Heh, your comment actually made me finally go and resolve a problem I’ve had since I got this laptop in 2020. I didn’t have SVM virtualisation acceleration enabled because that made Windows unable to boot somehow. A bit of twiddling after, it finally did! VirtualBox runs! Docker runs!

    …but why would I use Docker for something like this. Might as well blow the dust off of my FreeBSD virtual machine and run Forgejo there!


  • What’s the latest on Forgejo’s Windows builds? Last I checked there was no Windows build due to no volunteers for build/test - Gitea’s old build stuff should still be good.

    Which is a mild shame because Gitea’s Windows version was an insanely simple way to run it if you are a solo dev on Windows and need a private Git site. Drop the binary on an USB hard drive, run it on terminal, boom, done.

    (Currently contemplating just setting up a Raspberry Pi server.)


  • My father had a Brother laser printer. It outlived him. (…Anyway. Have you ever had to do Windows tech support for family? Not always nice. Ever had to do Windows printer tech support? Hoo boy. Ever had to do Windows printer tech support when the printer is hooked through a Centronics-to-USB adapter? Uggh. …though I was kind of surprised that Windows 10 still had built in drivers for the damn thing.)

    Me, I bought a Canon laser which technically has Linux drivers but damn me if I ever got it to print more than the CUPS test page. …actually I’d rather not talk about CUPS. I have too many bad memories about it. (You can’t escape the Printer Madness just by using Linux, oh no.)


  • Slackware 3.0 in 1996

    Then this new promising distro called Debian

    Got my own PC, went with Slackware again for some God-forsaken reason

    Debian again and that’s where I’ve stayed for most part - I tried using Ubuntu as a desktop laptop distro for a while but at some point I realised I should have installed Debian to begin with so I went with that there too