Live data from Hacker News

Threat actors expand abuse of Microsoft Visual Studio Code

jamf.com

301–306 of 306 posts

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#301
post #22
post #15

Earlier quoted context omitted.

> Coming from the perspective of an eclipse fan, why is VS code the defacto answer nowadays? Is eclipse good now? I used it 15 years ago. It took ages to start. It was a memory hog and it was dog slow besides. My entire team got RAM upgrades on our computers because the default company issued machines (which were quite good at the time) didn't have enough RAM to use eclipse properly. I can't imagine why it went out o…

How much ram did you have, and when was this? I remember being extremely happy with Eclipse on an 8GB machine - this was back in the jvm7 days. Heck, I did jvm6 development with Eclipse on Windows XP with 4GB of ram and was content. Eclipse gets a lot of automatic hate - I believe mostly since a lot of people first use it in university and struggled with their first real IDE. For years and years I had people telling…

yes, 15 years ago 8GB was normal on notebook. We though started to use it in the early naughts on 256Mb.

>Heck, I did jvm6 development with Eclipse on Windows XP with 4GB of ram and was content.

of course :)

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#302

Earlier quoted context omitted.

Until you actually do any of those things, an IDE is a fancy text editor.

and a 747 is a nice bed until you fly it. Doesn't mean it's overkill and a plane.

That's an absurd comparison, and you know it. Until an IDE actually performs some task that requires more advanced functionality, like analyzing a complex existing project to open without anything cached, compiling, profiling, etc. it is literally just editing text files. The only IDE that I use that takes anywhere CLOSE to the amount of time that Eclipse does to get moving is Unreal Engine. Any Jetbrains IDE, X Code, Visual Studio... all blow it away. I just opened a project in Visual Studio 2022 on a portability-focused laptop from 2018-- from click to the project open screen, it was about 3 seconds. From the project open screen to having an existing project completely open, it was 3 or so more seconds. On an 8 year old, tiny, not-optimized windows laptop.

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#303

Earlier quoted context omitted.

File access isn't the same as tool access. You need to run tools on your ssh host as well. And a devcontainer does indeed equal a (docker) container. The name is very specific and describes shipping a full developer environments so that 'you' do not have to install gcc-toolset-15, or boost 1.83, or mold, or python 3.11, and so on. https://containers.dev/

> File access isn't the same as tool access. Running tools remotely isn't the same as remote editing, so you'll have to forgive the misunderstanding. > You need to run tools on your ssh host as well. `ssh user@remote tool`. Indeed, the tool you run on the remote host could be a text editor in itself.

Interesting. Something to think about. Thanks.

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#304

Earlier quoted context omitted.

If you're using vim as an IDE (which is if course perfectly doable), then why does it matter if startup time is 50 or 1000 ms. You typically leave them running. > Yet I'm doing the same thing instantly or near instantly. Does vim somehow allow LSP servers to index faster? Or are you not actually doing the same thing?

Why are you leaving them running? Because they are slow to load? Yes, Neovim supports LSP and it is very very fast. I'm not sure why any of this is surprising. We're talking about the same company who is speeding up their file browser by loading it at boot time rather than actually trying to fix the actual fucking problems. Why is it surprising that everything else they make is slow and bloated as shit (even more as…

The point of LSP is that neovim is using the same servers for this as vscode. So I guess you work on smaller projects or with languages that have faster (usually meaning less fully featured) LSP servers.

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#305

Earlier quoted context omitted.

I suspect that you're relying too heavily on the user here. Even for myself, a very experienced developer, I don't have a flash of insight over what my risk exposure might be for what I'm opening at this moment. I don't have a comprehensive picture of all the implications, all I'm thinking is "I need to open this file and twiddle some text in it". Expecting us to surface from our flow, think about the risks and make…

[flagged]

Please don't cross into personal attack, regardless of how wrong someone is or you feel they are.

https://news.ycombinator.com/newsguidelines.html

Re: Threat actors expand abuse of Microsoft Visual Studio Code

#306

Earlier quoted context omitted.

The point of an IDE is that it does stuff a simple text editor does not.

Sure, but as noted elsewhere, the IDEs generally don't "do stuff" by default just on opening a file folder. VSCode, by default, will run some programs as soon as you open a folder.

Even something as simple as syntax highlighting is a vector.
Post reply on HN