3 ms·

Yep. The devs make random breaking changes all the time. They don't have any issue with doing it since they post breaking changes ahead of time.. but who actual

by chaps 6y ago

Yep. The devs make random breaking changes all the time. They don't have any issue with doing it since they post breaking changes ahead of time.. but who actually watches for these things? It's super frustrating

ehsankia 6y ago
I don't think posting ahead of time justifies it. Unless there are clear reason for a breaking change, having some code to parse old config into new one, or at the very least convert the first time an old config is seen, is pretty trivial compare to the amount of time wasted by every single users manually converting their config.
- nightcracker 6y ago
  Beyond that, tmux is (for me and probably many others) critical software used constantly when SSH'ing into many different boxes. Different boxes running different versions of tmux. Making it impossible to share one config file everywhere - you either need to have multiple config files for each version or simply drop any custom config that isn't cross-version compatible.
capableweb 6y ago
> but who actually watches for these things On the other hand, who is using any linux-like OS on a daily basis and upgrades major software versions when they have work to do? I usually only do full system upgrades (including essential software like tmux, vim and such) only when I know I have spare time in case there is things breaking, as 1 out of 10 times, something will break/be deprecated/have changes somehow.
- chaps 6y ago
  Upgrade time often happens when new features are needed for some project. So, yeah, it gets in the way of work ;)
  - capableweb 6y ago
    What kind of projects do you work on where new features to tmux are needed/required? Or put the other way around, what features in tmux were absolutely required for you to complete a project?
    - chaps 6y ago
      ...apt-get upgrade, friend.
      - capableweb 6y ago
        Yeah I get if you work on `apt` itself your use case might be a bit different. Although I'm not quite sure on what `apt` depends on from `tmux` but I digress.
        chaps 6y ago
        Hm. That's not what apt-get upgrade does. Can't tell if you're trolling, but I digress.
        capableweb 6y ago
        Sorry, I'm not following along at all but don't think it matters anymore. I got the impression that you are working on `apt`, and you're using `tmux` in some way when you're are working on `apt`. So when `tmux` releases a new change, you're unable to keep working on `apt` until X. But, thinking about it, none of this makes sense, and not sure why apt is mentioned at all, seems I misunderstood you?
        chaps 6y ago
        My point was that running `apt-get upgrade` is used in the process of installing packages besides tmux. For example some random postgres extension for something I'm working on, plus its respective dependencies. That process often needs a blanket `apt-get upgrade`, and very occasionally that installs a new version of tmux which isn't compatible with the old version's configuration file, breaking it in ugly ways. So then I have to fix tmux instead of whatever it was I was doing the original upgrade for. As a daily linux user, your original point doesn't make much sense in this light, since upgrading is a part of work.

by chaps 6y ago

ehsankia 6y ago

I don't think posting ahead of time justifies it. Unless there are clear reason for a breaking change, having some code to parse old config into new one, or at the very least convert the first time an old config is seen, is pretty trivial compare to the amount of time wasted by every single users manually converting their config.

nightcracker 6y ago
Beyond that, tmux is (for me and probably many others) critical software used constantly when SSH'ing into many different boxes. Different boxes running different versions of tmux. Making it impossible to share one config file everywhere - you either need to have multiple config files for each version or simply drop any custom config that isn't cross-version compatible.

capableweb 6y ago

> but who actually watches for these things On the other hand, who is using any linux-like OS on a daily basis and upgrades major software versions when they have work to do? I usually only do full system upgrades (including essential software like tmux, vim and such) only when I know I have spare time in case there is things breaking, as 1 out of 10 times, something will break/be deprecated/have changes somehow.

chaps 6y ago
Upgrade time often happens when new features are needed for some project. So, yeah, it gets in the way of work ;)
- capableweb 6y ago
  What kind of projects do you work on where new features to tmux are needed/required? Or put the other way around, what features in tmux were absolutely required for you to complete a project?
  - chaps 6y ago
    ...apt-get upgrade, friend.
    - capableweb 6y ago
      Yeah I get if you work on `apt` itself your use case might be a bit different. Although I'm not quite sure on what `apt` depends on from `tmux` but I digress.
      - chaps 6y ago
        Hm. That's not what apt-get upgrade does. Can't tell if you're trolling, but I digress.
        capableweb 6y ago
        Sorry, I'm not following along at all but don't think it matters anymore. I got the impression that you are working on `apt`, and you're using `tmux` in some way when you're are working on `apt`. So when `tmux` releases a new change, you're unable to keep working on `apt` until X. But, thinking about it, none of this makes sense, and not sure why apt is mentioned at all, seems I misunderstood you?
        chaps 6y ago
        My point was that running `apt-get upgrade` is used in the process of installing packages besides tmux. For example some random postgres extension for something I'm working on, plus its respective dependencies. That process often needs a blanket `apt-get upgrade`, and very occasionally that installs a new version of tmux which isn't compatible with the old version's configuration file, breaking it in ugly ways. So then I have to fix tmux instead of whatever it was I was doing the original upgrade for. As a daily linux user, your original point doesn't make much sense in this light, since upgrading is a part of work.