6 replies

1. Khalid ⚡ 5 min later

   @zachleat Do you think the JavaScript community is self-aware that they’ve poured all their energy into a tool ecosystem they don’t own?

   1. Zach Leatherman 2 hr later

      @khalidabuhakmeh do you mean the editor ecosystem or the framework ecosystem? I’m not sure. I’m tempted to blame the erosion of privacy norms in the US. EU folks seem to take a more principled approach, thankfully.

      1. Khalid ⚡ 2 hr later

         @zachleat Well, mostly the editor ecosystem, but I fear the line between the two begins to blur when you talk about LSP implementations.

         Most LSP implementations have a thick veneer of VSCode around them, which, imho reduces choice in tooling for the majority of folks.

         1. Zach Leatherman 2 hr later

            @khalidabuhakmeh this is my first time hearing about LSP 👀👀👀

            1. Khalid ⚡ 2 hr later

               @zachleat Oh dear… scan the article again. TL;DR: Some language servers being pushed have restrictive licensing, which means they can only be used within VSCode.

               I think this will be the standard approach moving forward.

               More info: https://langserver.org/ (fun activity: Search for Microsoft on the page)

               1. Zach Leatherman 3 hr later

                  @khalidabuhakmeh whew, yeah. Hm. My personal experience is that I’m pretty editor fluid. I’ve switched editors many times in my career. If I had to fast forward twenty years I’d guess that future-me will be recommending vim (though I don’t use it now) 😅