Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VS Code uses 13% CPU when idle due to blinking cursor rendering

github.com

Post reply on HN
Print view View original

781–790 of 801 posts

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#781

Post by allover »

allover wrote: post #775
allover wrote: post #770

Earlier quoted context omitted.

Yes it is sad that it is one of those topics that HN users seem incapable of discussing objectively. Meanwhile Electron usage grows and grows, and will continue to until someone comes up with a viable alternative.

If you disagree, tell me what I should use instead of Electron, that is feasible to use for a small team to have a wide platform reach, and with a community comparable to even just the 'React' part of web dev. The drive-by downvotes really just prove my point.

Yeah, thought so.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#782

Post by kuschku »

agumonkey wrote: post #501
kelvin0 wrote: post #418

Earlier quoted context omitted.

Nice foot gun story. If you had a T1 at the time, you would never had noticed such a pitfall.

I often advise to write code on "obsolete" tech. It makes every bit of cruft obvious.

I test all of my apps on an old Moto G, second generation, on throttled mobile internet (64kbps).

That’s the average worst case user.

This also means I notice massively if an app has hardcoded timeouts, or loads massive amounts of data.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#783

Post by dEnigma »

krylon wrote: post #398
Zenst wrote: post #361

Earlier quoted context omitted.

IBM spent a humongous amount of man hours upon the running man in smit under AIX, many of those consumed with making sure it ran correctly on all systems of various speeds without the animations going crazy. Alas I don't have exact man hours, but that was what one of the engineers told me a nearly 2 decades ago now. Hopefully somebody else has more detail upon this as one of the earliest examples of progress animatio…

Broken Sword let you play Breakout during the installation; it was such fun (I had not played Breakout in a long time at the point) I was almost sad when the installation was finished. ;-) I have often wondered since why this was not a more popular way to deal with long running installers.

Not quite the same thing, but DVDFlick lets you play Tetris while your DVD is being authored and burned, which was a nice suprise.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#784

Post by kuschku »

bananaboy wrote: post #665
jdonaldson wrote: post #232

Earlier quoted context omitted.

Except we're using divs , markup elements originally intended for research documentation, and using them to emulate modern UI techniques. I don't mind abstractions, but we should at least be using something built to task.

The most egregious example of abuse of technology for me is the browser version of Wolf3d, where they used divs to essentially replicate the vertical column drawing of a raycasting engine: http://3d.wolfenstein.com/

That game only works in the US, as it seems.

But if you set the cookies

    document.cookie = "age_checker=pass; expires=Thu, 18 Dec 2037 12:00:00 UTC; path=/";
    document.cookie = "is_legal=yes; expires=Thu, 18 Dec 2037 12:00:00 UTC; path=/";
It does work elsewhere, too. (Otherwise it just redirects to your local wolfenstein info site)

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#785

Post by eru »

michel-slm wrote: post #494
Zenst wrote: post #361

Earlier quoted context omitted.

IBM spent a humongous amount of man hours upon the running man in smit under AIX, many of those consumed with making sure it ran correctly on all systems of various speeds without the animations going crazy. Alas I don't have exact man hours, but that was what one of the engineers told me a nearly 2 decades ago now. Hopefully somebody else has more detail upon this as one of the earliest examples of progress animatio…

One Linux distribution used to let you play Breakout during installation, but I forgot which one. Caldera, maybe?

Don't most Linux installation just let you use your computer normally during installation?

(And by normally I mean, as booted from a LiveCD.)

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#786

Post by audidude »

digi_owl wrote: post #778
audidude wrote: post #754

Earlier quoted context omitted.

Interesting how one person is a common denominator in all those interactions ;)

And most of the comment gets ignored for a cheap retort, as expected.

you've mentioned something i've not heard about without linking to it or providing a name to help me find it myself. so i'm not sure what you'd like from me.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#787

Post by heinrich5991 »

Sharlin wrote: post #666
biggiesmalls wrote: post #583

Earlier quoted context omitted.

>> text editors built on the web stack cannot rely on the OS text caret Can you explain in simple terms why this is the case? Why on earth not?

Because you can't just ask the OS to "please paint text caret here thankyou", and browsers do not expose a powerful enough native text editing control. So you end up reimplementing one in JS/HTML/CSS, including the caret.

The WinAPI function SetCaretPos seems to do that: https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#788

Post by abritinthebay »

8draco8 wrote: post #183
abritinthebay wrote: post #151

Earlier quoted context omitted.

VS Code is faster than Atom (by... a lot) tho? Especially with large files, but just in general. Speed is the main reason I can't stay using Atom for more than a few hours. It's awful. VS Code is snappier than Sublime Text ffs...

VSC is not even close of being as snappy as Sublime Text. Sublime also dominates when opening large files (2GB+) and searching trough them.

On my Mac that just wasn't true.

Sublime had the edge in a couple of cases, but when opening large files (esp JS bundles) it crawled. Took over a minute to open one.

Same file in VSCode - maybe a couple of seconds. Maybe.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#789

Post by abritinthebay »

stinos wrote: post #246
8draco8 wrote: post #183

Earlier quoted context omitted.

VSC is not even close of being as snappy as Sublime Text. Sublime also dominates when opening large files (2GB+) and searching trough them.

Agreed, except for the domination; true on linux afaik but not on windows: working with the large files is ok but opening them takes ages. VSC is definitely faster there.

My experience on the Mac too. Working with was ok (mostly) not great but ok, but opening was very slow.

Re: VS Code uses 13% CPU when idle due to blinking cursor rendering

#790

Post by abritinthebay »

Philipp__ wrote: post #171
abritinthebay wrote: post #151

Earlier quoted context omitted.

VS Code is faster than Atom (by... a lot) tho? Especially with large files, but just in general. Speed is the main reason I can't stay using Atom for more than a few hours. It's awful. VS Code is snappier than Sublime Text ffs...

Nope, it's not snappier than Sublime.

shrugs

Is for me. Not by a lot, and not in every case, but overall? Is for me.

Post reply on HN