WEBVTT 1 00:00:00.270 --> 00:00:02.820 So like GitHub Copilot, 2 00:00:02.820 --> 00:00:07.820 Cursor provides smart, AI-driven suggestions. 3 00:00:07.920 --> 00:00:10.320 Now, also like GitHub Copilot, 4 00:00:10.320 --> 00:00:12.780 Cursor does not just do that for the line 5 00:00:12.780 --> 00:00:14.490 you are currently working on, 6 00:00:14.490 --> 00:00:17.760 but also for other lines in your code base. 7 00:00:17.760 --> 00:00:21.030 It makes predictions regarding the next edit 8 00:00:21.030 --> 00:00:22.770 you'll likely wanna make. 9 00:00:22.770 --> 00:00:25.320 GitHub Copilot also has this feature now, 10 00:00:25.320 --> 00:00:26.610 but they didn't always have it, 11 00:00:26.610 --> 00:00:29.070 they basically copied it from Cursor, 12 00:00:29.070 --> 00:00:31.530 and Cursor pioneered this feature. 13 00:00:31.530 --> 00:00:35.520 And, of course, you'll have to simply try and find out 14 00:00:35.520 --> 00:00:38.400 which editor works better for you, 15 00:00:38.400 --> 00:00:40.380 so if you like the predictions 16 00:00:40.380 --> 00:00:42.960 by GitHub Copilot more than Cursor's 17 00:00:42.960 --> 00:00:45.810 or the other way around. 18 00:00:45.810 --> 00:00:48.120 Now, for the Cursor team, 19 00:00:48.120 --> 00:00:51.030 ultimately, their vision is, 20 00:00:51.030 --> 00:00:53.100 they said that in a podcast, 21 00:00:53.100 --> 00:00:55.110 that you can work on a code base 22 00:00:55.110 --> 00:00:57.780 by just hitting tab, tab, tab all the time. 23 00:00:57.780 --> 00:01:01.470 So that they predict the next edits very, very well, 24 00:01:01.470 --> 00:01:05.850 and you therefore can move through a code file quickly 25 00:01:05.850 --> 00:01:09.753 and make all those edits based on those smart predictions. 26 00:01:10.800 --> 00:01:15.800 For example, if I change content here to text, let's say, 27 00:01:16.200 --> 00:01:18.390 it's there after, it's a bit subtle to see, 28 00:01:18.390 --> 00:01:21.393 but it there after highlights content down here. 29 00:01:22.350 --> 00:01:23.880 It has a red background. 30 00:01:23.880 --> 00:01:26.400 And on the right, it opens a little popup 31 00:01:26.400 --> 00:01:29.610 where it shows me what it wants to change. 32 00:01:29.610 --> 00:01:31.470 It wants to change the argument 33 00:01:31.470 --> 00:01:34.200 that's passed to the write method to text. 34 00:01:34.200 --> 00:01:38.880 So from content to text, it wants to make this change. 35 00:01:38.880 --> 00:01:40.380 So if I hit Tab now 36 00:01:40.380 --> 00:01:43.560 after changing this parameter name here to text, 37 00:01:43.560 --> 00:01:47.013 if I hit Tab now, even though my cursor is here, 38 00:01:48.120 --> 00:01:50.340 you see this here changed to text, 39 00:01:50.340 --> 00:01:53.040 and now it jumps down here to the bottom, 40 00:01:53.040 --> 00:01:54.570 highlights this in red, 41 00:01:54.570 --> 00:01:57.240 and suggests that it wants to rename this here 42 00:01:57.240 --> 00:01:58.413 to text as well. 43 00:02:00.240 --> 00:02:03.060 So if I hit Tab a couple of times, it goes down there. 44 00:02:03.060 --> 00:02:04.320 Next it highlights this 45 00:02:04.320 --> 00:02:07.230 because it understands that this parameter here 46 00:02:07.230 --> 00:02:10.173 needs to be renamed to be in line with this name. 47 00:02:11.550 --> 00:02:14.400 So all I'm doing here is I'm hitting Tab all the time 48 00:02:14.400 --> 00:02:17.970 to accept all these changes until at some point it's done. 49 00:02:17.970 --> 00:02:20.940 And that's an important difference 50 00:02:20.940 --> 00:02:22.740 compared to GitHub Copilot. 51 00:02:22.740 --> 00:02:24.510 It can be confusing at first, 52 00:02:24.510 --> 00:02:26.190 but once you get used to it, 53 00:02:26.190 --> 00:02:31.140 this is really something that can get you into a nice flow 54 00:02:31.140 --> 00:02:34.350 where you can make changes across your entire code file 55 00:02:34.350 --> 00:02:36.693 rapidly by just hitting Tab. 56 00:02:37.770 --> 00:02:40.620 Of course, you should also take a brief look 57 00:02:40.620 --> 00:02:42.570 at least what's about to change, 58 00:02:42.570 --> 00:02:45.720 but then you can just hit Tab to accept all these changes. 59 00:02:45.720 --> 00:02:49.440 So Cursor really tries to take this code completion feature 60 00:02:49.440 --> 00:02:51.570 to the next level and complete 61 00:02:51.570 --> 00:02:53.490 and change parts of your code you 62 00:02:53.490 --> 00:02:55.683 are not even working on right now. 63 00:02:57.000 --> 00:02:59.130 But as you see, it always shows you 64 00:02:59.130 --> 00:03:00.090 what it's about to change 65 00:03:00.090 --> 00:03:01.920 and you confirm it with the Tab key. 66 00:03:01.920 --> 00:03:04.260 So it's not automatic, but it's smart. 67 00:03:04.260 --> 00:03:08.883 And that's a really neat feature that's built into Cursor.