News for hackers. Stuff that matters.

A comment on VS Code uses 13% CPU when idle due to blinking cursor rendering. Parent comment

Re:VS Code uses 13% CPU when idle due to blinking cursor ren... by captainmuon on Thursday March 23, 2017 @12:44PM (#13941434)
> For instance I wanted to be able to display PDFs directly in VSCode. I went to look for a plugin, and there was one.

You could have done that 20 years ago with COM components already. There was a thriving ecosystem where you could get a component for just about everything.

Similar technologies were available on other platforms than Windows, like Bonobo (Gnome), Kparts (KDE), and whatever Mac had.

It's a bit of a shame that component frameworks have gotten such a bad reputation (for complexity and insecurity), I think they are very misunderstood.

[ Parent | on HN ]
Re:VS Code uses 13% CPU when idle due to blinking cursor ren... by z3t4 on Friday March 24, 2017 @06:01AM (#13947788)
You also had to pay 100$ per copy of the COM component. Most of the web stuff is free, and you can just right click and view source. In NodeJS and NPM there are hundreds of thousands of components/modules that you can use for free.
[ Parent | on HN ]