• 1 Post
  • 22 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle









  • ¿Does Gimp on Windows finally use the same interface as the Linux version? But either way while I have learned to use Gimp over time and appreciate it the interface certainly has rough edges. For me that’s particularly noticeable when it comes to handling different layers and controlling which part of the interface has focus.

    Some functionality is also quite hidden and exploring the interface isn’t so useful for finding it, often I found myself prompting a search engine instead. But I can also see that Gimp is a complex program with a ton of functionality and it’s very hard to make the interface intuitive for every type of user at once.



  • One reason to keep in mind is backwards compatibility and the expectancy that every Linux system has the same basic tools that work the same.

    Imagine you have a script running on your server that uses a command with or without specific arguments. If the command (say tar) changes its default parameters this could lead to a lot of nasty side effects from crashes to lost or mangled data. Besides the headache of debugging that, even if you knew about the change beforehand it’s still a lot effort to track down every piece of code that makes use of that command and rewrite it.

    That’s why programs and interfaces usually add new options over time but are mostly hesitant to remove old ones. And if they do they’ll usually warn the others beforehand that a feature will deprecate while allowing for a transitional period.

    One way to solve this conundrum is to simply introduce new commands that offer new features and a more streamlined approach that can replace the older ones in time. Yet a distribution can still ship the older ones alongside the newer ones just in case they are needed.

    Looking at pagers (programs that break up long streams of text into multiple pages that you can read one at a time) as a simple example you’ll find that more is an older pager program while the newer less offers an even better experience (“less is more”, ¿get the joke?). Both come pre-installed as core tools on many distributions. Finally an even more modern alternative is most, another pager with even better functionality, but you’ll need to install that one yourself.








  • For Syncthing I had to add a bunch of rules to my firewall to allow the necessary connections between my PC and smartphone. And for that I had to find, install and familiarize myself with a fire wall first. And after that ensure that the fire wall service is running always. Summa summarum: it’s not something that is likely to work out of the box.

    The great thing about Syncthing is that once you have it set up properly it really does work. It silently does its thing in the background and I never think about it

    Haven’t used LocalSend yet but I imagine it’s going to be much less of a pain if the traffic is all routed through the Brower.


  • It’s so dumb that JSON doesn’t officially have comments.

    So much this.

    Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a “hack” I would sometimes add extra objects to store strings (the comments). But that’s super dicey as you don’t know if it somehow breaks the parsing. You’re also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

    Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.