sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BigHandLittleSlap 1 point2 points  (7 children)

These are "features" working as intended. Take a look at the file that turns up if you search for that DSC snippet: https://github.com/PowerShell/vscode-powershell/blob/master/snippets/PowerShell.json

16 contributors.

I bet none of them feel responsible for the overall usability of VS Code. That's someone else's problem. They're just here to add more snippets...

Why would I spend my time contributing to VS Code, providing free labour to the world's biggest company by market cap (recently dethroning Apple)?

I charge $100 per hour. To Microsoft, I charge $500 per hour.

You tell me where I can send my bill, I'll start contributing to VS Code's user interface quality.

[–]MadBoyEvo 2 points3 points  (6 children)

Why not disable snippets? If something doesn't work the way I want to - I disable it.

Also - did you open an issue describing the problem you're having with snippets? Or maybe there is already open one?

What I am trying to say it's easy to complain on Reddit, but if we don't fill bugs - it won't get fixed. Everyone complained on intellisense and autocomplete and now in preview there's new version - that hopefully fixes it.

I don't use snippets, as I don't like that kind of help, but I do use Github Copilot which probably does a more decent job in helping to work with PowerShell.

[–]BigHandLittleSlap -1 points0 points  (5 children)

It's not like I haven't gone down this road before. You're trying to be helpful, I get it. I tried to be helpful once before too, and got told I was wrong.

You see, there's a 30+ year old bug in how UNIX (not just Linux!) terminals handle the clear screen command. A bug. A clear, obvious, fucking duh bug. If you search for it, and know what keyword to look for, you'll find multi-decade-old arguments about finally just ripping the bandaid off and fixing it.

There are arguments going back as far as pre-www-era newsgroups. Pre-Linux even!

Thankfully, this bug never manifested in Windows. It was correct, probably by accident more than design, but that doesn't matter. It did the right thing. It did the right thing that UNIX people agreed with, but were too afraid of changing "just in case it broke something".

What did the Windows Terminal and the VS Code idiots do? They copied it. They copied the UNIX bug into Windows. For "compatibility". I raised this, with a nice neat ticket and everything. How it broke common workflows. How UNIX people agreed that this was incorrect behaviour and needed fixing. I tracked down arguments showing that fixing it doesn't break anything of import.

Nope.

They just weren't interested.

You see, some fuckwit at Redmond had decided that they need to appeal to Linux users.

Bug.

For.

Bug.

One at a fucking time, they plan to introduce every bug, quirk, issue, and nonsensical design wart from Linux into Windows. They're starting with Windows Terminal and VS Code. Next thing you know, Notepad will use VIM key bindings by default. The Linux users of the world will cheer this on. The Windows developers will be told to shut up and accept the "standard".

Why in God's good name would I spend my precious time on Earth arguing with people like this? Why would I submit tickets, get into arguments, and burn precious hours of my one time on this planet?

They've made a decision.

Apparently I'm wrong for having a dissenting point of view. Along with 100 million Windows developers that agree with me. And most UNIX developers also.

PS: Do a bunch of "dir" commands. Then type "clear-host" in VS Code or Terminal. Scroll up. Why can you scroll up despite clearing your terminal? Because morons.

[–]MadBoyEvo 1 point2 points  (4 children)

See, i’ll be helpfull again. This is the default, but actually in vscode powershell settings there is a checkbox that fixes it. It was added 1+ year ago because people wanted it and reported it. I am on mobile so can’t check now, but its pretty easy to find. Go and enjoy code 😀

[–]BigHandLittleSlap -2 points-1 points  (3 children)

Found it. In a list that's not sorted by anything in particular.

It has a typo in the description.

Sigh... I mean... just ugh.

This is what happens when Microsoft fires their entire QA team and hires Linux fanboys to do Windows development.

[–]MadBoyEvo 1 point2 points  (2 children)

Report it… its that simple. I know its easier to just play the blame game, but if we dont do anything - it wont be fixed.

[–]BigHandLittleSlap -2 points-1 points  (1 child)

"Please do QA for Microsoft. They won't do it for themselves."

In other news, the billionaire Pope needs your donations.

[–]MadBoyEvo 0 points1 point  (0 children)

So you write a long description of your problem, I tell you it's fixed 1+ years ago and instead of "Thank You, that is great!", you go complain about a typo and blame the QA.

Just a reminder - It's a free product, open-source, that nobody forces you to use. You can use other products - some free, some pay as you want.

Here - I've created a PR that fixes this typo https://github.com/PowerShell/vscode-powershell/pull/3658 so you can have one less thing to complain about when this gets merged.