6 ms·

This is totally pedantic, but LSP stands for “Language Server Protocol”. I think they mean LS (or Language Server)

• aaronbrethorst 2y ago
  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.
• binary132 2y ago
  Yeah, that detail of terminology always bothered me a bit. That said, we do call HTTP servers that, not “Hypertext servers”. Then again, we don’t call an HTTP server “an HTTP”. :)
  • notpushkin 2y ago
    “LSP server” doesn’t sound too bad!
• pimlottc 2y ago
  Coming from a different background, LSP to me means “linguistic service provider” (i.e. human language translation). I wasn’t familiar with this LSP [0] at all. 0: https://en.m.wikipedia.org/wiki/Language_Server_Protocol https://en.m.wikipedia.org/wiki/Language_Server_Protocol
• kristoff_it 2y ago
  Yep, you never see me mix the two things in the body of the post. I deliberately did it in the title to save some space.
• mg74 2y ago
  Salsa sauce!
  • devnonymous 2y ago
    Chai tea!
• samatman 2y ago
  I think this is applying pedantry in the wrong place. Language Server, you say? Ok, it serves a language. But how? Using LSP? Ok, sounds like an LSPS. The client would be an LSPC. LSP is not the only language an LS can speak, it's overwhelmingly dominant, yes, but the Dart language used to speak its own protocol, and SLIME is also a distinct protocol for what we may reasonably describe as language servers. Similarly, although HTTP(S) is the only hypertext protocol in common use, we don't call it a Hypertext Server, we call it an HTTP server. I think it's more than alright to elide LSPS as just LSP. At this point that's idiomatic. But my point is that the term is anti-redundant, unlike ATM Machine and other usual suspects in this perennial Internet topic: it elides, rather than duplicates, information.
  • catlifeonmars 2y ago
    Still shamelessly (mis)applying pedantry “A new HTTP LSP…” reads like a new protocol being introduced, which is inaccurate, hence my original complaint. Try this on for size: “A new HTTP…”. Sounds weird right?