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

What Electron-related problems have you had with VSCode? I've been using it as my primary for a few years now and it's been nothing but stellar. And that integration sounds incredibly cool.


When I tried VSCode a year ago, I found it to have an input lag, compared to sublime.

Given your comments, I just installed it right now to try it out again. I like the built in terminal & git integration. Code search performance is excellent (w/ code hosted in WSL) due to this new client/server model... and there was no input lag in the editing window.

The only lag I noticed was in CTRL-P selector, but that's a small compromise given the client/server model solves the real time waster.

I think I'm going to try it out over the next few weeks :)


The electron hate really is getting old. vscode and some other electron apps run far faster than many comparable programs with a more traditional architecture. Yes electron could be considered inelegant, but so can a great many things in computing. If it works, we should use it.


Yep. If anything, "old-school" Visual Studio is the one that feels bloated by comparison, despite being a native app. Software quality cannot be reduced to the choice of language or framework.


It kind of is, then again VSCode doesn't do even half of VS is capable of.


The two doesn't even play in the same category:

"source code editor" vs full fledged IDE

It doesn't make much sense to compare the two in general imho.


VSCode is truly a full-fledged IDE for TypeScript at least, and via plugins it can play the part for several other languages, including Rust. Mostly those depend on the quality of their Language Server implementations.


Which was exactly my point, I said "in general" but for some precise use cases, the comparison actually makes sense.


It doesn't make much sense to compare VSCode and VS though.


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.


Font rendering is a bit blurry.


When did you last see this? I ask because VSCode fixed some blurry font rendering bugs a couple of months back.


I haven't experienced this, but I mostly use it on a Mac. What OS are you on?


Technically, on Macs, all font rendering is blurry. :) https://pandasauce.org/post/linux-fonts/


Technically, there should be more HiDPI monitors on the market. I'm using now 24" monitor with 4k resolution, scaled 200%, and fonts are perfect :)




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

Search: