Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not an Electron-related problem, just a general issue: What made me give up on VSCode after trying to make it work again(this March) was the fuzzy search just not being very good in my Rails projects. I can ctrl-shift-r in sublime and get to the method definition I want in 4-5 characters. It's probably my primary code navigation technique: see a thing, wanna check the def, 1-2 seconds later I'm there.

There's some VSCode extension that claims to mimic this but the fuzzy search seems much worse and it just doesn't quite work. Yes you can use the solargraph extension to sort of go to the def in vscode and it does all sorts of cool things, but I just never got into it.

It seems like a small thing but I just couldn't get over it, because I do it so often.

The main other difference is I much prefer the GitSavvy Sublime text extension to VSCode's built-in git handling. Particularly how I can see a summary of the commit I am making in GitSavvy whereas there doesn't seem to be a way to get all the file changes in one screen in VSC(though to be fair I didn't look around much for a way to do this, there probably is an option somewhere).

That being said if fuzzy search was working the same as in Sublime, I'd probably switch to Code.



Yeah, its level of support for different languages definitely varies. For TypeScript it feels like a paid IDE. For Rust and Clojure it works quite admirably, since it's the most prominent free (graphical) option for each. For Python, it's... underwhelming. That's too bad about Rails, but I also can't say I'm super surprised.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: