4 ms·

That's a clarification that you can take all the way to the bank—or at least to the AT machine.

• kreetx 2y ago
  Yup, much like pull request vs merge request - the "wrong" one is here to stay.
  • imjonse 2y ago
    On gitlab at least it is merge request, but the platform using the "wrong" term is more popular.
    • hyperbrainer 2y ago
      Is it really "wrong" if everybody understands what you mean using the term?
      • rauli_ 2y ago
        It can create confusion with people who are still learning to use Git.
      • imjonse 2y ago
        It's not wrong, but "wrong" as both comments above had :)
• ffsm8 2y ago
  Another instance of this are DNS - which is pretty much always called domain name server server (DNS server) Though you can at least have an argument there, as the first server could theoretically be the process that's running on the hardware/virtual server (which would be the second server).
  • Colex 2y ago
    Except that DNS does not mean Domain Name Server, but Domain Name System. So DNS Server makes sense (Domain Name System Server).
    • ffsm8 2y ago
      Fair. even the original rfcs from 198x only write about domain name servers though, which is why the DNS server is still a misnomer of the same kind, even if my attempt of rationalizing it failed - as that's the only thing you've called into question with that. Because if domain name system server makes sense to you, then language server protocol server has to make sense in the same way, as that's literally the same concept
      • echoangle 2y ago
        LSP Server does make sense, the problem is that the title calls it a "HTML LSP", not a "HTML LSP Server". The thing described is a server, not a protocol.