• 0 Posts
  • 18 Comments
Joined 2 months ago
cake
Cake day: August 31st, 2025

help-circle




  • You can, and should do that. Here’s what that looks like: toolbox run -c <toolbox-name> <command>

    All of my development tools are in a toolbox, including my IDE (Sublime Text). I created a standard .desktop file so that I can launch it like any other application, and it works perfectly, with a proper Icon and everything. Example:

    [Desktop Entry]
    Version=1.0
    Type=Application
    Name=Sublime Text
    GenericName=Text Editor
    Comment=Sophisticated text editor for code, markup and prose
    Exec=/usr/bin/toolbox run -c devel /opt/sublime_text/sublime_text %F
    Terminal=false
    MimeType=text/plain;
    Icon=/home/user/.local/share/applications/SublimeText.png
    Categories=TextEditor;Development;
    StartupNotify=true
    StartupWMClass=sublime_text
    

    To run something on the host from inside a toolbox, you can use flatpak-spawn:

    $ toolbox enter ...
    $ flatpak-spawn --host <command> <args>
    

    You can even use that to (awkwardly) run something in another toolbox using the same command above:

    flatpak-spawn --host toolbox run -c <other-container> <command>
    

    Sublime text specifically has support for custom build commands. Sometimes, I’m using it to develop something in a different toolbox than the one sublime is installed in. So in my custom build script for the project, I add a check to enter the correct toolbox before executing the build. Here’s what that looks like:

    TARGET_TOOLBOX=example
    source /run/.containerenv
    if [ "$name" != "${TARGET_TOOLBOX}" ]; then
    	echo "SWITCHING CONTAINER $0 $@";
    	flatpak-spawn --host toolbox run --container ${TARGET_TOOLBOX} /usr/bin/env zsh -c "$0 $@";
    	exit 0;
    fi
    
    #proceed with build...
    

    This container/toolbox workflow is far superior to anything else, as it makes it trivial to quickly test whether your code works on a different distros/versions. It all just works with your existing tooling/local workflows once you learn how to work with the tools. There really is nothing you can’t do.

    …and that’s for development, which is the most difficult scenario for this type of thing. For regular every day users, immutability just works without requiring people to learn anything new besides reaching for flatpak instead of apt/dnf/pacman/etc.


  • Discover is probably the worst app in the entire KDE suite. It’s the only aspect of the Linux desktop that frustrates me, and I’m nearing 10 years of full time Linux desktop usage.

    Oh, you accidentally opened Discover? Now you gotta sit and twiddle your thumbs while it updates/downloads a bunch of stuff very slowly with no way to interrupt it. It also locks the system package manager, so you literally cannot do anything else package management related until Discover slowly decides to finish doing something you never asked it to do.






  • I first discovered Linux in middle/highschool back when Ubuntu was the hot shit and they had that awesome Gnome 2 desktop. I loved the vibes, but didn’t stick with it because I didn’t know what to do. Then just over the years I’d occasionally install it for a few days and give it a shot, learning more and more, even installing Arch Linux once (back when it was actually a challenge).

    Switching to Linux was inevitable for me, I think. As the years rolled on, Windows got worse and worse while my understanding/confidence with Linux got better and better. I don’t remember what the final thing was that convinced me to finally go 100% Linux on all my devices, but I did around ~2017 or 2018 with zero regrets.

    So I think that if there’s a path for people to learn Linux at a comfortable pace, without the trauma of going all in, they’ll also find it impossible to resist. The dynamic of Windows becoming worse while Linux becomes better is still holding strong.








  • This article was written by an anonymous/throwaway Medium account. For all we know, it was written by a PR firm they hired. Corporate propaganda has zero credibility, and the anonymity makes it impossible to verify that it’s anything else.

    And if anything, now that time has proven that Trump/Vance were, in fact, worse than everyone was saying, it’s further reason to hate Proton for using their influence/reach to support them. Did it help them win the whitehouse? Hard to say, but even in the best case scenario, it comes off as a lame, opportunistic move to advertise their services to MAGA and profit off political turmoil.