It just reorders the autocomplete list. This is kind of underwhelming.
Visual Studio IntelliCode
11–20 of 49 posts
Re: Visual Studio IntelliCode
#12I read that page, watched the vid, and really don't understand what the benefits of this are. Currently use ReSharper and it seems to do a pretty awesome job of predicting what I want. Whoever is promoting this needs to give better examples...
It's looking at github projects with more than 100 stars:
https://visualstudio.microsoft.com/services/intellicode/
I guess everybody is wondering why this even exists. Sounds like a typical "solution in search of a problem" to me, and it probably only got green-lit because it mentioned "AI" in the pitch deck ;)
Re: Visual Studio IntelliCode
#13Wasn't that what the nefarious Kite extension was trying to do ?
Re: Visual Studio IntelliCode
#14Earlier quoted context omitted.
Also wondering the same thing. What does this accomplishes over Resharper (for example) ?
It's free, for one. Other than that: this looks absolutely horrible. I don't want AI to make suggestions. I know which methods I want, and which names I want to give stuff.
What about people who don’t know the methods?
Wouldn’t better suggestions be helpful for those learning a language, any language?
I could learn C# or F# in half the time, for example.
This might not be the tool, but I can imagine AI being extremely useful in software development.
Re: Visual Studio IntelliCode
#15This feature also exists in Visual Studio 2019 and I actually like it. The UI is unobtrusive and the suggestions are very often correct in my fairly extensive experience with it. All the negativity seems to be forgetting that this isn't removing anything, only augmenting an existing feature. Additionally I can see this being very useful to new developers who are less familiar with the language and what can or should be done.
Re: Visual Studio IntelliCode
#16This is just an ad for dirkstrauss' website. uBlock origin blocks 34 ads.
Now I'm interested to see, how this page looks with ad-blocker disabled.
Re: Visual Studio IntelliCode
#17I've never seen any IDE as good as IntelliJ IDEA when it comes to Auto suggest, and it has no real AI, just deterministic understanding of the project's source tree and dependencies, an indexed AST, how the type system works, and what's in scope at the cursor. In other words, two classes both called 'List' should not show up when I start typing 'List', if only one of them can possibly be relevant in context. A lot of IDEs, especially in refactoring, for Java often appeared to use string comparison. So you'd do a system wide refactor of say interface 'Foobar', and it would match completely different interfaces called 'Foobar' that had no relation to what's under the cursor.
It's this almost 100% exact matching that develops into a rapid muscle memory where you learn to trust the IDE, and non-deterministic algorithms which have say, a 1% failure rate, tend to be annoying.
Re: Visual Studio IntelliCode
#18Earlier quoted context omitted.
It's free, for one. Other than that: this looks absolutely horrible. I don't want AI to make suggestions. I know which methods I want, and which names I want to give stuff.
What about people who don’t know the methods? Wouldn’t better suggestions be helpful for those learning a language, any language? I could learn C# or F# in half the time, for example. This might not be the tool, but I can imagine AI being extremely useful in software development.
If suggestions are to be made i'd rather have them be made by the designers of the APIs/languages, especially those are have been around for some time and have developed better approaches for doing things already possible previously but in a worse way.
For example imagine you have an API that Foos Stuff, the initial version could have been FooStuff but it turned out that after 10 years of active use, the approach was slow for modern use cases and the only way to improve it was to change the API to BeginStuffFooing, ProcessStuffFooing and FinishStuffFooing but still keep the original FooStuff for backwards compatibility.
After 10 years of use, an AI-driven approach that data mines existing codebases (especially popular codebases that are more likely to be mature/old codebases) will be more likely to use FooStuff than Begin/Process/FinishStuffFooing, thus people will be steered towards FooStuff instead of the better approach.
Something that is driven explicitly by the API designer can start recommending Begin/Process/FinishStuffFooing from the moment it is available and recommend against introducing FooStuff in new code (it could even show up a tooltip or whatever with a "here is how to use the new approach if you already know the old approach" link).
Re: Visual Studio IntelliCode
#19I 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 bui…
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.
Re: Visual Studio IntelliCode
#20Earlier quoted context omitted.
What about people who don’t know the methods? Wouldn’t better suggestions be helpful for those learning a language, any language? I could learn C# or F# in half the time, for example. This might not be the tool, but I can imagine AI being extremely useful in software development.
If suggestions are to be made i'd rather have them be made by the designers of the APIs/languages, especially those are have been around for some time and have developed better approaches for doing things already possible previously but in a worse way. For example imagine you have an API that Foos Stuff, the initial version could have been FooStuff but it turned out that after 10 years of active use, the approach was…
Isn't that what the Obsolete attribute is for? Or similar attribute/test driven enforcement of migration to new approaches.
It mines your own codebase, not public ones.