Live data from Hacker News

Microsoft please get your tab to autocomplete shit together

ivanca.github.io

141–150 of 153 posts

Re: Microsoft please get your tab to autocomplete shit together

#141
post #117

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.

Hi from the VS Code team - I recently went into detail about why we did this in https://github.com/microsoft/vscode/issues/282268#issuecomme... . We believe it'll be beneficial overall and go a long way in lowering the bar to make the terminal less intimidating for newcomers. Conflicts with muscle memory was always a big concern which is why we made extra effort to be able to turn it off, the comment below that one o…

This a byproduct of metric-driven development. The result is a creepy manifestation of force-fed features backed by "telemetry" (action and result logging, and sometimes keystroke or string logging), but I don't place any blame on this developer; this is the way it has been at that company for a while and that horse has long since left the barn.

Certainly this may not even be intended gesture, but it will result in unknowable metric of users being insulted by the half-baked forced nature of these product changes.

Re: Microsoft please get your tab to autocomplete shit together

#142
post #117

Earlier quoted context omitted.

Hi from the VS Code team - I recently went into detail about why we did this in https://github.com/microsoft/vscode/issues/282268#issuecomme... . We believe it'll be beneficial overall and go a long way in lowering the bar to make the terminal less intimidating for newcomers. Conflicts with muscle memory was always a big concern which is why we made extra effort to be able to turn it off, the comment below that one o…

I've had to take a beat to find the right words as all the frustration in the issue ticket impacted me too which has left a very bad taste in my mouth after being initially curious and open to the new feature. I think you're doing a disservice to newcomers by creating a new method of autocompletion. And I say that as somebody who has mentored a lot of newcomers in high school, University, and now professionally. Very…

> I think you're doing a disservice to newcomers by creating a new method of autocompletion

Or a feature to lock users into their tools?

Re: Microsoft please get your tab to autocomplete shit together

#144

True madness for average user here is that they removed Intellisense plugins and force copilot but gives a seriously unusable quota for tab-completion, for non-paid users. I just totally don't get it.

No they didn't. They removed intellicode - an AI derivative (228 points, 10 days ago, 180 comments) https://news.ycombinator.com/item?id=46286383

> IntelliCode is NOT IntelliSense

https://news.ycombinator.com/item?id=46290607

Re: Microsoft please get your tab to autocomplete shit together

#145
post #78

Earlier quoted context omitted.

> Windows Search requires a DNS lookup WHY? Why? Why. I’m seriously asking. Who thought that was a good idea? Who?! FIRE THEM. NO USER ever in the history of Windows users ever said: “I want to search the contents of my computer, but windows search is too fast; can you please make windows search extremely slow, make it omit things that I know exist, and also make it search the internet? Also, I want you to index my l…

The best thing about windows 11 is that if you hit the windows key, and type 'restart', it searches for 'restart' on Bing . Please give me the name, rank, and serial number of the PM who thought this was a good idea. I will use all my meager fortune to make sure that nobody will want to hire them for PM work ever again .

Easiest I've found is Windows+X, then 'u' for 'Shut Down or Restart' then 'r' for retart. Win+X, u, r.

Re: Microsoft please get your tab to autocomplete shit together

#146
post #117

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.

Hi from the VS Code team - I recently went into detail about why we did this in https://github.com/microsoft/vscode/issues/282268#issuecomme... . We believe it'll be beneficial overall and go a long way in lowering the bar to make the terminal less intimidating for newcomers. Conflicts with muscle memory was always a big concern which is why we made extra effort to be able to turn it off, the comment below that one o…

First of all, I appreciate and respect you coming here and defending your choices. That said:

I think that bar-lowering is not really something that Terminal users want, if they wanted simplicity they wouldn't be in a terminal in the first place, at least that holds true for a large portion of the Terminal users.

Sure there are always the new users, who may benefit from some hand-holding. But why don't you ask first if people want their hand held? Normal terminal users are looking for a way to control their computer in a more direct fashion, which makes them faster. They seek a more predictable interface, by moving closer to the true language of the computer itself, by learning a bit about how it works inside and subsequently adapting oneself to it.

You have chosen to alienate a large group of highly knowledgeable users for a user group that may be mostly a myth.

What would make more sense is to provide a switch for "noob mode", while leaving the core experience alone. I for one already hate the difference between my normal terminal when it comes to ctrl-c/ctrl-v and pasting with select/middle-click. This current change feels like a slap in my face.

Re: Microsoft please get your tab to autocomplete shit together

#147

Earlier quoted context omitted.

I've had to take a beat to find the right words as all the frustration in the issue ticket impacted me too which has left a very bad taste in my mouth after being initially curious and open to the new feature. I think you're doing a disservice to newcomers by creating a new method of autocompletion. And I say that as somebody who has mentored a lot of newcomers in high school, University, and now professionally. Very…

> I think you're doing a disservice to newcomers by creating a new method of autocompletion Or a feature to lock users into their tools?

No, it's really not that good a feature and turning it off improves my experience so I don't care if they're the only ones with it. That said, if it's part of the open source, when better. And even if it was, I can't complain that a business made a program has a unique feature to attract users.

Re: Microsoft please get your tab to autocomplete shit together

#148
post #23

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.

Yeah for anyone else (especially Mac and Linux users) who recently had this frustration thrust upon you: Go into VSCode settings and search for terminal integration > uncheck.

The specific setting is `terminal.integrated.suggest.enabled`.

Re: Microsoft please get your tab to autocomplete shit together

#149

Why do people still spend time worrying about M$ stuff…

Microsoft stuff is universally dogshit. The amount of time/money we burn on making Azure work as it’s supposed to is insane. I will never willingly give Microsoft money.

If you hate Azure, wait until you try AWS.

(I hate(d) Azure, and then I was forced to try AWS.)

Re: Microsoft please get your tab to autocomplete shit together

#150

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.

It’s so weird, vscode worked flawlessly for me for years and after migrating to neovim a month or two ago I keep seeing complains. Has there been a change lately and in the project, or is it just internet bias?

They broke it again today with release 1.107 which throwns a weird shadow when I resize the window in Gnome. Got fed up with it, so I pinned the package to 1.106.
Post reply on HN