3 ms·

As it happens, the first time this came up in #lad I was like "another name is sensible!" ("how about osm? like, One Session Manager!" (that being, at least, Br

As it happens, the first time this came up in #lad I was like "another name is sensible!" ("how about osm? like, One Session Manager!" (that being, at least, British humour)), but, by the second time, I was resigned to the fact that renaming what would be the same (but more robust protocol) to another acronym would be pointlessly confusing to users (and devs). NSM was a hopelessly overloaded term already. It's interesting to see the instance of HN groupthink speculation (and lack of google fu) there has been in this comment section. Folk should come idle/chat in #lad. It's available via Matrix.

ww520 5y ago
Because people here look dimly on those taking other's hard work with underhanded tactics. The name NSM and its binary files are the BRAND of the original project and the original developer spent lots of time to build the project and build the brand. All the integration with the names required work and time built over time that the original developer had put in. Don't tell me it's just a name and has no value. If so, you guys won't pick the same name and same binary names. Fork the project and pick another name. Spend the effort to market and build the integration with the new name. No one would have a problem.
- mxmilkiib 5y ago
  Underhanded tactics? JML was abusive and has exaggerated. I think it should be clear to anyone the relationship; the README mentioned JML from the get go, it's not framed as NON related, there is reference client and daemon, and it's just the same acronym because there's no reason to change. The new projects name is New Session Manager.
  - ww520 5y ago
    Picking the same acronym based on a similar name is VERY underhanded, especially when the acronym is used throughout as the name for the project. The term NSM is used more than a dozen times while Non Session Manager is used 3 times in their about page. NSM is basically the identity of project. http://non.tuxfamily.org/wiki/Non%20Session%20Manager http://non.tuxfamily.org/wiki/Non%20Session%20Manager Using the same acronym and the same binary file names to push out Non from the distribution is very underhanded. This looks like a deliberate aim to confuse the users and taking over the project code and identity. It's not cool. I don't know JML and don't know his development style. Since he has been gracious enough to open source his project, I assume he's generous enough to share his hard work with others. If people don't like his style, fork the project with a different identity and compete on the merits, rather than stealing his project's identity with confusion.
    - mxmilkiib 5y ago
      Push out non nsm from a distribution? Mate, it was the individual distro packagers that decided enough was enough on that front. You are trying to argue a course of action that would just have confused both users and devs.

ww520 5y ago

Because people here look dimly on those taking other's hard work with underhanded tactics. The name NSM and its binary files are the BRAND of the original project and the original developer spent lots of time to build the project and build the brand. All the integration with the names required work and time built over time that the original developer had put in. Don't tell me it's just a name and has no value. If so, you guys won't pick the same name and same binary names. Fork the project and pick another name. Spend the effort to market and build the integration with the new name. No one would have a problem.

mxmilkiib 5y ago
Underhanded tactics? JML was abusive and has exaggerated. I think it should be clear to anyone the relationship; the README mentioned JML from the get go, it's not framed as NON related, there is reference client and daemon, and it's just the same acronym because there's no reason to change. The new projects name is New Session Manager.
- ww520 5y ago
  Picking the same acronym based on a similar name is VERY underhanded, especially when the acronym is used throughout as the name for the project. The term NSM is used more than a dozen times while Non Session Manager is used 3 times in their about page. NSM is basically the identity of project. http://non.tuxfamily.org/wiki/Non%20Session%20Manager http://non.tuxfamily.org/wiki/Non%20Session%20Manager Using the same acronym and the same binary file names to push out Non from the distribution is very underhanded. This looks like a deliberate aim to confuse the users and taking over the project code and identity. It's not cool. I don't know JML and don't know his development style. Since he has been gracious enough to open source his project, I assume he's generous enough to share his hard work with others. If people don't like his style, fork the project with a different identity and compete on the merits, rather than stealing his project's identity with confusion.
  - mxmilkiib 5y ago
    Push out non nsm from a distribution? Mate, it was the individual distro packagers that decided enough was enough on that front. You are trying to argue a course of action that would just have confused both users and devs.