Bahman M. (@bahmanm@mastodon.social)
mastodon.social
Attached: 1 image My fellow software engineer, It's the year 2024. Please store your #Linux #desktop application configurations ONLY in `$XDG_CONFIG_HOME`. NOT in `$HOME` or other non-standard or obsolete places. May #FreeDesktop be your guide. https://www.freedesktop.org/wiki/Specifications/ #Programming #DevOps #SysAdmin

Shameless plug: I am the author.

  • dinckel@lemmy.world
    1172·
    6 months ago

    Golang puts shit specifically in $HOME/go. Not even .go. Just plain go.

    Why is it so difficult to follow industry standards

    • Laser
      316·
      6 months ago

      That’s what happens when you don’t set $GOPATH I think

        • Laser
          133·
          6 months ago

          It makes it insofar better to me that you have the option to change it. You can’t change Mozilla programs to use anything but .mozilla (apart from modifying the source code of course) so for me seeing the folder is at least a way of telling me that the variable is unset.

          The better question is which folder is suited the best to store the stuff that goes into $GOPATH

          • fmstrat@lemmy.nowsci.comEnglish
            7·
            6 months ago

            Just because something is worse, doesn’t make the other thing good. A sane and standard default, as others have mentioned, is a small bar to meet.

      • dinckel@lemmy.world
        20·
        6 months ago

        Of course, but that’s not the point. There should be a sane default, and there isn’t one

    • atzanteol@sh.itjust.worksEnglish
      121·
      6 months ago

      Go pisses me off with that. I separate projects the way I want but go wants every project written in go in one big directory?

      • dinckel@lemmy.world
        2·
        5 months ago

        I really didn’t like this either. It’s quite surprising, because the rest of Go tooling is quite nice. Not having a venv, or at least something like pnpm-style node_modules is weird

        • jollyrogue@lemmy.ml
          1·
          5 months ago

          Why would go have a virtual environment or dep tree like node_modules equivalent, it’s not interpreted or dynamically linked.

          With modules, dependencies can be vendored.

          • dinckel@lemmy.world
            1·
            5 months ago

            Obviously it’s not, but you have to download all this shit somewhere before compilation. That’s the whole point

    • Eager Eagle@lemmy.worldEnglish
      5·
      6 months ago

      off the shelf go was too annoying for me

      Nowadays I set GOENV_ROOT to an XDG location and use goenv instead.

      • WolfLink@sh.itjust.works
        15·
        6 months ago

        What I want in $HOME are the following directories:

        If I’m on a GUI-based environment:

        • Desktop
        • Documents
        • Downloads

        In general:

        • .local
        • my_junk_folder_i_made

        I’d like everything else to live within something like ~/.local thanks

        • dan@upvote.au
          8·
          6 months ago

          Maybe Linux should have .local and .roaming folders like Windows. local = only useful on this system, roaming = good to sync across systems. Config would be in .roaming if it’s not machine-specific.

          • rotopenguin@infosec.pubEnglish
            6·
            5 months ago

            The only practical difference between Local and Roaming and LocalLow is that developers randomly pick one and dump your game saves in there.

            • dan@upvote.au
              6·
              6 months ago

              There’s some stuff in~/.config that’s specific to the computer. KDE is a good example - a lot of KDE apps mix config and state in the same file. There’s some solutions for syncing these files, like https://github.com/VorpalBlade/chezmoi_modify_manager which is an addon to Chezmoi that can exclude particular keys when storing an INI-style config file in Git.

              I’m sure there’s some config files in there that are entirely specific to the computer. Things like the Wayland per-monitor scaling settings are in there somewhere I think.

              There’s also things like data files that you may want to keep in sync across machines. They’re not really configs.

          • jollyrogue@lemmy.ml
            1·
            5 months ago

            There is a .local folder these days.

            Profile roaming hasn’t been solved aside from NFS mounts. I guess Syncthing might work.

            • dan@upvote.au
              1·
              5 months ago

              I know .local exists - My comment was more about .roaming which would be nice to exist, but doesn’t currently exist.

              Profile roaming hasn’t been solved aside from NFS mounts. I guess Syncthing might work.

              I’m using Chezmoi to sync some dotfiles, scripts, etc. to a Git repo and that seems to work well enough for me. I’m not syncing much yet, though.