←back to thread

310 points skarat | 2 comments | | HN request time: 0.777s | source

Things are changing so fast with these vscode forks I m barely able to keep up. Which one are you guys using currently? How does the autocomplete etc, compare between the two?
Show context
heymax054 ◴[] No.43961400[source]
90% of their features could fit inside a VS Code extension.

There are already a few popular open-source extension doing 90%+ of what Cursor is doing - Cline, Roo Code (a fork of Cline), Kilo Code (a fork of Roo Code and something I help maintain).

replies(2): >>43961415 #>>43966500 #
wrasee ◴[] No.43961415[source]
The other 10% being what differentiates them in the market :)
replies(1): >>43961424 #
heymax054 ◴[] No.43961424[source]
Of course. Are they useful enough though for people to install an entirely new software?
replies(2): >>43961790 #>>43981744 #
gkbrk ◴[] No.43961790[source]
Since installing entirely new software is just downloading Cursor.AppImage from the official website and double-clicking on it, it's not a large hassle for most users.

If you're on Arch, there's even an AUR package, so it's even less steps than that.

replies(1): >>43963270 #
bryanlarsen ◴[] No.43963270[source]
appImage is useless for development since it only has access to globally installed development tools and environments.
replies(1): >>43966523 #
1. gkbrk ◴[] No.43966523[source]
That's not true.

AppImages aren't sandboxed and they can access the rest of the system just fine. After all, they're just a regular SquashFS directory that get mounted into a /tmp mount and then executed from there.

replies(1): >>43966660 #
2. bryanlarsen ◴[] No.43966660[source]
So you're saying that the Cursor appImage is done poorly? I'd believe that.