Visual Studio IntelliCode

Re:Visual Studio IntelliCode by YuukiRey on Tuesday June 04, 2019 @04:35AM (#20093099)

I appreciate all attempts at improving this kind of auto suggesting but for me simple buffer based string completion is still vastly superior to anything VSCode offers out of the box (I work as a front end dev). Way too often VSCode suggets methods and snippets that are totally irrelevant while ignoring a string that's just a few lines await. So far no configuration settings helped with that. So bottom line vim's built-in buffer completion is more efficient at least for the work I do.

TabNine is actually the only thing that I could see myself switching to.

[ Parent | on HN ]

Re:Visual Studio IntelliCode by Crinus on Tuesday June 04, 2019 @06:19AM (#20093596)

I like Lazarus' approach where it tries its best to provide you intelligent completion but if that fails it also does token/keyword/identifier based completion from what it can find in all open files and remembers from previously open files.

And it always, always, ALWAYS puts any word it knows/guesses that starts with the characters i type at the front before making any other suggestion.

And all that in interactive practically instant speeds. How the hell Visual Studio takes ages (ie. often several seconds) to complete a word i already typed a few moments ago on a 4.2GHz 7700K machine with 32GB of RAM whereas Lazarus happily completes words even on a puny Raspberry Pi, i don't know.

Anyone who writes IDEs should work for at least 6 months with Lazarus to understand how to do things right and if their IDE still provides a worse editing experience (i'm not expecting the entire WYSIWYG GUI and object design as this isn't really something everyone cares about, although it'd be nice) after that then they are doing something very wrong. I have issues with Lazarus with the overall UX being very messy, but the editing experience is the best i've seen.

[ Parent | on HN ]

Re:Visual Studio IntelliCode by Dayshine on Tuesday June 04, 2019 @06:05AM (#20093537)

If you're using Intellicode in Visual Studio with C#, I'm afraid I don't really believe you. Intellicode strongly prioritises nearby code elements.

Could you give an example of a situation where it's completely missing the point?

VS Code's default completion is strictly buffer based, so no sure what you mean there either.

[ Parent | on HN ]

Re:Visual Studio IntelliCode by YuukiRey on Tuesday June 04, 2019 @06:39AM (#20093675)

I have a bunch of screenshots I shared in our work slack channel. First of all I am talking about Visual Studio Code rather than Visual Studio. I should have mentioned that, sorry. Intellicode is also available for VSC so I figured it would be relevant here.

The screenshot I posted a while back showed me exporting something at the of the file and I had typed `Det` at which point it suggested some random functions from random APIs. Then I had `Detail` at which point no suggestions were offered. At `Detaile` it finally gave me `DetailedProgress` from the same file about 50 lines higher up.

This is a frequently recurring theme that it takes so long to actually suggest mere names (~ strings).

[ Parent | on HN ]

Re:Visual Studio IntelliCode by Dayshine on Tuesday June 04, 2019 @09:03AM (#20094538)

My understanding is that completion in VS Code for C# is provided by Omnisharp, which yeah, I agree, seems to be slow and inconsistent.

I've written a language server extension for VS Code (not for C#), and the completion lists I provide are better than those I get in C#/F# while writing the server, it's bad :/

[ Parent | on HN ]