text stringlengths 0 2.02k |
|---|
[2271.52 --> 2279.56] And then finally, we have that marketplace where you can make a Node app and then distribute it so it can get in front of millions of sellers and be an option for them to adopt. |
[2279.56 --> 2280.34] Very cool. |
[2280.44 --> 2280.68] All right. |
[2280.70 --> 2288.48] If you want to learn more, head to developer.squareup.com to dive into the docs, APIs, SDKs, and to create your Square developer account. |
[2288.78 --> 2290.56] Start developing on the platform seller's trust. |
[2290.92 --> 2293.24] Again, that's developer.squareup.com. |
[2293.24 --> 2314.02] So, Nick, you mentioned that you were waiting for the Lua stuff to land or to be official. |
[2314.16 --> 2318.16] 0.5 came out this summer, July 2nd, I believe. |
[2318.26 --> 2319.16] A huge release. |
[2319.16 --> 2320.86] 4,000 commits, as I mentioned before. |
[2321.30 --> 2322.74] 1,000 of those reports. |
[2323.24 --> 2324.16] From Vim. |
[2324.24 --> 2325.62] But lots of new stuff. |
[2326.60 --> 2328.80] And the community rejoiced. |
[2328.88 --> 2330.60] I mean, this must have been a long time coming, TJ. |
[2330.66 --> 2332.20] How much work went into this release? |
[2332.42 --> 2334.56] Well, yeah, there was a lot of work. |
[2334.70 --> 2343.98] There was probably, if I had to take a guess, probably, I don't know, three or four weeks of time of me just answering when will NeoVim 0.5 come out. |
[2344.10 --> 2346.98] You know, just replying to messages like that online. |
[2346.98 --> 2351.24] We started a meme on my Twitch channel when people would ask that. |
[2351.24 --> 2353.24] We did exclamation, the rule. |
[2353.50 --> 2361.82] And then that took a bot command back and it explained that every time someone asks about NeoVim 0.5 release, the release date has to be pushed back one day. |
[2361.82 --> 2374.42] Yeah, but in all seriousness, I mean, it's been a long time coming and it, you know, was a culmination of a lot of sort of really long term project and vision that the team had. |
[2374.42 --> 2379.50] I can't take credit for all of it or even probably, you know, I can't take credit for most of it or anything. |
[2379.72 --> 2389.24] But, you know, seeing things like the LSP come to fruition, there's some fun history there where you can go dig up some of the original issues. |
[2389.24 --> 2405.42] And my first PR probably in 2016 or 2017, where I proposed a lot of the first ideas about how we would put LSP inside of NeoVim and have it be in such a way that it still is the spirit of Vim. |
[2406.02 --> 2411.86] You know, that it's not we're trying to smash everything in here and re-implement every wheel that we can. |
[2412.32 --> 2414.00] How can we do it in that way? |
[2414.00 --> 2417.20] So for me, it's been very fun to see that finally released. |
[2417.36 --> 2423.58] You know, it's been in my head for a long time and other people who helped along the way to finally implement it. |
[2423.80 --> 2440.32] And then as well, you know, putting in TreeSitter, which has also been sort of a long term vision about making NeoVim as an editor understand the text at a much higher and more, I'd say, interesting or semantic level than just like strings of characters. |
[2440.32 --> 2440.76] Right. |
[2440.80 --> 2442.24] Which is one of the goals of TreeSitter. |
[2442.24 --> 2447.20] So let's focus in on LSP, the language server protocol. |
[2447.38 --> 2452.42] So this part didn't make the Vim show, but I did ask each person what they FOMO'd from other editors. |
[2453.18 --> 2454.82] And we wanted to keep it tight. |
[2454.88 --> 2456.02] So we dropped that section out. |
[2456.14 --> 2460.24] But I'll tell you, Drew Neal mentioned LSP specifically in VS Code. |
[2461.52 --> 2464.94] Yeah, well, I come back to language servers again. |
[2464.94 --> 2469.20] I mean, about a year or two ago, I started learning TypeScript. |
[2469.74 --> 2474.10] And I know that TypeScript has a very good language server. |
[2474.24 --> 2481.66] I mean, pretty much language servers and VS Code and TypeScript were all kind of invented under the same roof. |
[2481.66 --> 2483.52] And so they're very, very well integrated. |
[2483.52 --> 2489.52] And I knew that I wanted to understand what a good TypeScript development experience is. |
[2490.30 --> 2494.56] And so I made a decision not to use Vim while I was learning TypeScript. |
[2494.92 --> 2499.10] I thought, OK, VS Code is an editor that's very well positioned for beginners. |
[2499.10 --> 2509.60] And while I'm being a beginner in TypeScript, I'm going to be a beginner in VS Code as well and just learn the way that good language server integration would feel like. |
[2510.00 --> 2518.80] So that I can sort of take that learning and bring it back to Vim so that when I make that step of, OK, I'm going to now switch all my TypeScript development back over to Vim. |
[2519.02 --> 2520.22] I know what I'm looking for. |
[2520.82 --> 2526.70] For those who don't even know what LSP is, can you just explain what it is, where it came from, and then we'll talk about it in context in NeoVim. |
[2527.26 --> 2527.70] Yeah, sure. |
[2527.70 --> 2530.16] So LSP is a protocol designed by Microsoft. |
[2530.46 --> 2536.66] It's actually what Microsoft's VS Code uses to communicate and basically get the language smarts that it has. |
[2537.36 --> 2543.56] Its big goal is, if you think about, you have M editors, right, in N languages. |
[2543.56 --> 2549.16] And when you want to implement support for the next language, you have to implement that M times, right? |
[2549.16 --> 2559.28] And so I think as developers, we're very familiar with M times N problems being very difficult and feeling intractable and also not fun to solve, right? |
[2559.28 --> 2564.70] Because even if you solve it once, you feel you're going to have to solve it N times again later. |
[2564.70 --> 2576.92] So LSP is basically a protocol designed to talk from editors to some sort of server that's giving you information about what you're editing, right? |
[2576.92 --> 2582.48] So if you have your cursor on somewhere in a document, you can say, hey, what's the definition of this? |
[2582.64 --> 2585.30] And so there's a protocol, text document slash definition. |
[2585.58 --> 2588.62] You send that over the wire to something that's running. |
[2588.82 --> 2589.84] It can be anything you want. |
[2589.88 --> 2591.32] It can be on your machine, another machine. |
[2591.38 --> 2591.90] Doesn't matter. |
[2591.90 --> 2598.50] Just a protocol that you send over the wire and ask, hey, what's the definition of this text document at this position? |
[2598.78 --> 2604.32] And it will return you back a list of possible definitions or one, you know, whatever the result is. |
[2604.42 --> 2606.70] And you'll be able to go there in the editor, right? |
[2606.70 --> 2609.60] So the editor will receive that response and know what to do. |
[2609.82 --> 2614.40] So this is really powerful because in theory, it's not always exactly like this. |
[2614.78 --> 2621.20] It'll turn the problem from M times N to M plus N, which is a much better problem to solve. |
[2621.20 --> 2625.08] And it's probably more like M plus N plus, you know, Z, right? |
[2625.14 --> 2626.50] There's some extra work still. |
[2626.66 --> 2627.02] That's a Z. |
[2627.56 --> 2629.00] Yeah, it still has to happen. |
[2629.16 --> 2635.76] You know, like some language servers have specific commands that only make sense for their language, you know, or things like that. |
[2636.12 --> 2636.72] But that's OK. |
[2636.80 --> 2639.68] That's still a much more fun problem to solve. |
[2639.86 --> 2641.62] And so that's sort of the basics of what happened. |
[2641.76 --> 2649.94] And like in the context of NeoVim, what we saw was that this is sort of in a lot of ways just like an interface to your editor. |
[2649.94 --> 2663.66] And that was one of my big pushes for how we should think about LSP inside of NeoVim is this is really just defining a standard way that is shareable between other pieces of technology in how you can talk to your editor. |
[2663.88 --> 2664.04] Right. |
[2664.04 --> 2673.02] So I recently implemented something for my work at Sourcegraph where I implemented like a go to definition over LSP. |
[2673.44 --> 2679.96] But what it does instead of running something locally, it asks this external program where the definition of this thing is. |
[2680.34 --> 2680.44] Right. |
[2680.46 --> 2683.04] And so that was basically like a way for me to do that. |
[2683.04 --> 2688.54] And I didn't I mean, obviously, I knew how to move to the file and all these other things because I am familiar with NeoVim. |
[2688.80 --> 2690.52] But it doesn't have to be so. |
[2690.74 --> 2690.86] Right. |
[2690.92 --> 2693.34] So it allows this interface to do. |
[2693.52 --> 2696.30] And then if I can do another plug for Lua in here. |
[2696.36 --> 2696.56] Right. |
[2696.60 --> 2701.48] The way that we did this with Lua is that it's very easy because everything is just a function. |
[2701.48 --> 2714.34] You can replace a function with a basically set of parameters and as expected thing to happen and replace it with some new behavior that's more suited to your purpose. |
[2714.62 --> 2717.22] I'll give an example for that, which is in Golang. |
[2717.74 --> 2725.16] We have a bunch of stub or test implementations for some interfaces that we have at my work. |
[2725.48 --> 2729.90] I don't want to jump to those when I hit go to implementation. |
[2729.90 --> 2731.80] 99% of the time. |
[2732.26 --> 2738.00] So what I did was I can ask the LSP, hey, where are the implementations of this? |
[2738.40 --> 2750.48] I wrote some Lua code that walks through the results and says, if this file ends with underscore test or like underscore mock, discard it and throw that away from my results. |
[2751.08 --> 2753.56] Generally at work, we just have one result that remains. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.