5 ms·

I think LSP language server protocol and literate programming are a match made in heaven. A simple syntax like noweb and a LSP dispatcher which only handles th

by froh 4y ago

I think LSP language server protocol and literate programming are a match made in heaven. A simple syntax like noweb and a LSP dispatcher which only handles the noweb syntax elements and dispatches both text and code chunks to respective back ends; the LP LSP Server tangles the code chunks and presents the tangled code to the code specific LSP servers and does the mapping forth and back of the position-in-nw vs position-in-$code while passing all other communication through. especially now that we have DAP something like this would really make sense, wouldn't it?

junon 4y ago
Speaking anecdotally, I have nothing but issues with LSP. It's a pain to use, a pain to configure, gives sub-par results and is usually wraps with extra "features" that change how code gets edited between different languages (I know this is less LSP's fault). Not to dismiss the mountain of work people have put into it, but it feels very hacked together and clunky rather than a shining achievement.
- tuukkah 4y ago
  Case in point, Microsoft develops an editor (VSCode) and LSP so that N*M language integrations wouldn't be necessary. But in the development of their language (TypeScript), LSP support is not a priority (in part because LSP is inadequate in its current form): https://github.com/microsoft/TypeScript/issues/39459 https://github.com/microsoft/TypeScript/issues/39459
  - codethief 4y ago
    > We're working on this, albeit slowly. tsserver's implementation predates LSP so it's nontrivial work to move forward in a way that doesn't adversely affect old clients or result in code duplication.
    - tuukkah 4y ago
      Good to hear you're still committed. By "not a priority" I mean we have been waiting since this was published back in 2016: "[LSP] also means any developer can have a consistent editing experience for their favorite programming language on any tool – even if that tool isn’t VS Code." https://code.visualstudio.com/blogs/2016/06/27/common-language-protocol https://code.visualstudio.com/blogs/2016/06/27/common-langua... The original bug against Typescript was opened in 2016 as well: https://github.com/microsoft/TypeScript/issues/11274 https://github.com/microsoft/TypeScript/issues/11274
      - codethief 4y ago
        Note I merely quoted from the above Github ticket. :)
        tuukkah 4y ago
        I see. In that case, possibly replace "you" with "they" in my reply.

by froh 4y ago

junon 4y ago

Speaking anecdotally, I have nothing but issues with LSP. It's a pain to use, a pain to configure, gives sub-par results and is usually wraps with extra "features" that change how code gets edited between different languages (I know this is less LSP's fault). Not to dismiss the mountain of work people have put into it, but it feels very hacked together and clunky rather than a shining achievement.

tuukkah 4y ago
Case in point, Microsoft develops an editor (VSCode) and LSP so that N*M language integrations wouldn't be necessary. But in the development of their language (TypeScript), LSP support is not a priority (in part because LSP is inadequate in its current form): https://github.com/microsoft/TypeScript/issues/39459 https://github.com/microsoft/TypeScript/issues/39459
- codethief 4y ago
  > We're working on this, albeit slowly. tsserver's implementation predates LSP so it's nontrivial work to move forward in a way that doesn't adversely affect old clients or result in code duplication.
  - tuukkah 4y ago
    Good to hear you're still committed. By "not a priority" I mean we have been waiting since this was published back in 2016: "[LSP] also means any developer can have a consistent editing experience for their favorite programming language on any tool – even if that tool isn’t VS Code." https://code.visualstudio.com/blogs/2016/06/27/common-language-protocol https://code.visualstudio.com/blogs/2016/06/27/common-langua... The original bug against Typescript was opened in 2016 as well: https://github.com/microsoft/TypeScript/issues/11274 https://github.com/microsoft/TypeScript/issues/11274
    - codethief 4y ago
      Note I merely quoted from the above Github ticket. :)
      - tuukkah 4y ago
        I see. In that case, possibly replace "you" with "they" in my reply.