5 ms·
> Screw your conventions, we've always done it this way I don't understand this section heading. To me, software convention has the third meaning as shown on m
by toast0 3y ago
> Screw your conventions, we've always done it this way
I don't understand this section heading. To me, software convention has the third meaning as shown on merriam webster[1]:
> 3 d : an established technique, practice, or device (as in the theater)
In that case, that we've always done it that way establishes the technique, and the established technique is the convention.
To argue that non-desktop software should apply a desktop specification that they weren't involved in developing seems rather insane, especially since they are and have been following the established convention.
[1] https://www.merriam-webster.com/dictionary/convention https://www.merriam-webster.com/dictionary/convention
- mschuster91 3y ago> To argue that non-desktop software should apply a desktop specification that they weren't involved in developing seems rather insane, especially since they are and have been following the established convention. So what, stuff changes over time - and it's not that hard to migrate, either warn the user, or do the migration at first start. Good software should move with the times, not be perpetually frozen.
- vorpalhex 3y agoIf you force me to migrate, I'm probably ditching your software. The inability to keep a stable user contract is a deep flaw that impacts too much software these days. Respect the user.
- devnullbrain 3y agoMultiple options for configuration files is a well-trod, easy solution. You shouldn't have to migrate.
- INGSOCIALITE 3y agoEveryone should do what emacs does (and a lot of software does): first look for .emacs for a config … not there? Check .emacs.d … still not there? .config/emacs …
- tsimionescu 3y agoThat's not exactly what emacs does: if ~/.config/emacs isn't there, then it will default to creating ~/.emacs.d/ and ~/.emacs, even if the XDG env vars are set. Basically, emacs supports XDG config if you really want it to, but it's not the default way of using emacs. And of course, it only uses ~/.config/emacs, none of the other XDG folders. If you download a package from MELPA, that's still going to .config/emacs, as far as I know.
- arp242 3y agoBut also not without the downsides, because what do you do if multiple files are found? And how will you communicate that to the user, if at all? Lots of room for confusion here: "why aren't my changed taking effect?!", "where is this setting coming from, it's not in my file?!" and things like that.
- devnullbrain 3y agoStick it in the manpage. Neovim does this. Power users who care about non-standard configuration should be able to carry the burden of managing it.
- arp242 3y agoThings like bashrc and vimrc have been "standard" for decades; that's not a "non-standard configuration", it's what everyone uses today. And Neovim only supports ~/.config/nvim/init.vim judging from the manpage(?) If it doesn't then this only underscores my point that all of this is apt to lead to confusion. Either way, it had a clean break from Vim and didn't have to deal with people who have been using Neovim for decades (lots of things are different compared to Vim and it's not intended to be compatible in the first place).
- devnullbrain 3y agoBy non-standard I mean XDG home
- toast0 3y agoForced migrations always leave a legacy of pain. How many documents tell you to configure ssh with something in ~/.ssh/config and if the change is made, will now need to be changed to say put your config in one of many paths depending on the version you use? What if you migrate your config and then roll back to an earlier version? What if you use your home directory on multiple systems, some which have varying versions of the tool, loading the config from various places (network mounted home directories are a practice in some companies)? What if you don't upgrade for ten years, and the migration code is gone by then? What if you operate on a mix of systems of various ages, some which have the new path and some which have the old? What if the migration code has a security vulnerability? Personally, I don't see where the benefit is that pays for anywhere near any of this cost. Maybe if you're a desktop app that is within the scope of standards put out by the XDG, you might want to consider accepting this standard of theirs too; and sure, if you're a new application, seems like a might as well?
- JoBrad 3y agoI thought about this, too. One fix would be for ssh to make a solid process that walks you through setting up your ssh config. Then it could be placed anywhere you like, and the preference would be set. Those docs would just reference the setup switch or tool, instead.
- tsimionescu 3y ago10 year old docs would reference the newly developed SSH options?
- delta_p_delta_x 3y agoAuthor here. I had a gut feeling that heading was problematic, and I posted it anyway. I should rephrase that...
- bootlickdev 3y ago[flagged]
- rendaw 3y agoIt works for me. Established also has multiple meanings, but the most applicable one here says "generally accepted" [1]. Each listed piece of software has its own way of doing things, so speaking of _the_ established practice is wrong here, and I doubt I'd be able to list more than one of those off the top of my head, so _established_ hardly seems appropriate. And whether you agree with it or not, I doubt anyone understands "desktop" as meaning "GUI only" and not "for human users" in this context. I usually see it used contrastively as in "desktop" vs "server". Server software lives in `/usr` and writes to `/run` and `/var`, etc. [1] https://en.wiktionary.org/wiki/established https://en.wiktionary.org/wiki/established
- toast0 3y ago> And whether you agree with it or not, I doubt anyone understands "desktop" as meaning "GUI only" and not "for human users" in this context. Config files don't apply to only human users either, though. Automation also uses configs. And they've got to be somewhere. Some automation is desktop oriented, I'll acknowledge. If this standard came from Posix, sure, that applies generally across unix and linux to all programs great and small. If it comes from Linux Standards Base, I've got issues, cause I don't run Linux, but that at least clearly applies to all programs on Linux, packaged by a distribution and configuration file locations are obviously within the scope of LSB. But XDG is more or less the Xorg/Freedesktop peeps; how are config files for everything under the sun in their scope? There's lots of stuff in their scope, but this just seems out of the blue. Being not an exclusively Linux organization is somewhat helpful, but still. How is the XDG an authority on where to place config files when there was already a servicable location to put them (and the specification documentation doesn't even have a discussion of who they are, why their spec matters, how the values came to be, etc)
- delta_p_delta_x 3y ago> How is the XDG an authority I addressed this in the article: Linux devs not being able to accept some authority—in this case, XDG—is the source of the fragmentation in Linux and why even though we have a spec, there's still a solid 30%+ of programs that don't follow it. Yes, OpenSSH isn't a 'desktop' program, but there are dozens of desktop programs which use it as a backend. Forget Linux, for a moment: it creates `.ssh`on Windows. Windows doesn't have dot-files, and it never had. This is arrogance.