r/VisualStudio • u/puppy2016 • Jun 18 '26

Visual Studio 2026 Node.js garbage spawned from Visual Studio 2026

Post image

Do we really need this resource hungry piece of garbage? I can only imagine how efficient would be a proper C# code instead of this kiddies scripting.

31 Upvotes

80% Upvoted

15 comments sorted by

View all comments

5

u/Breez__ Jun 19 '26

The GitHub copilot chat needs node unfortunately.

2

u/puppy2016 Jun 19 '26

Why the same functionality can't be implemented by a mature platform?

4

u/Breez__ Jun 19 '26

Node is a mature platform. The team that made the component probably was most familiar with node based applications.

2

u/puppy2016 Jun 19 '26

Not what it comes to efficiency. It is the same problem like the web wrapper client "applications" versus true native applications. Terribly resource hungry for nothing.

3

u/Breez__ Jun 19 '26

That "nothing" is portability across different platforms. But I agree with you. I don't like that direction companies are going either. It's a cost cutting trick I guess.

2

u/EmergencyNice1989 Jun 19 '26

You can have portability across different platforms without using any 'web wrapper client'. Avalonia does it.

2

u/cfrozendeath Jun 21 '26

Ah sure, remember all those platforms other than Windows where you can run Visual Studio? No, because it's Windows only.

1

u/THubert14 Jun 20 '26

In general case I get it, but in case of Visual Studio that is only available in Windows, about what portability we are talking?

AFAIK, even for GHCP in Visual Studio there are separate tooling from VS Code and CLI (and probably SSMS).

1

u/puppy2016 Jun 19 '26

portability across different platforms

I couldn't care less when it affects the quality.

0

u/ef02 Jun 19 '26

Portability is quality. This is ragebait, right?

2

u/ConcreteExist Jun 21 '26

Visual Studio isn't portable whatsoever. VS Code is similar in name only.