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

671–680 of 801 posts

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

#671

Post by mercer »

ashark wrote: post #632
mercer wrote: post #220

Earlier quoted context omitted.

Over the past year or two Gmail has gotten really slow. I'm not sure what happened, because there are no new features I can think of that would cause this. It's gotten so bad that I'm considering moving to another provider or using a good old email app again.

Use the basic HTML version. It's worth the loss of a couple features from regular gmail or inbox for a much snappier UI (even with it fetching full new pages from the server all the time!)

I like my vim-style keyboard shortcuts thought :-/.

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

#672

Post by flukus »

jamesgeck0 wrote: post #620
flukus wrote: post #614

Earlier quoted context omitted.

That varies on the OS/driver/hardware, but IMO, the new AMD graphics drivers being in the kernel tree are the way to go, or something similar like a partnership between MS/AMD/Nvidia. As a consumer it's incredibly frustrating to have a buggy driver and not know who is responsible. Is it MS? Windows comes with a lot of drivers so blaming MS seems fair. Is it the hardware manufacturer? Sometimes you can get the latest…

You're making this harder than it needs to be. All Windows drivers are signed. Blame the party that signed the buggy driver.

The point is, users will blame windows because they don't know what a graphics driver is or that they have one, so MS took steps to avoid people thinking windows is buggy. MS has a long history of this, going as far as reproducing bugs.

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

#675

Post by KirinDave »

problems wrote: post #531
KirinDave wrote: post #492

Earlier quoted context omitted.

I'm glad at least we made fun of both sides. I really wish there was a good option for GUI toolkits. Nearly all are either too primitive to make more than freshmen college (or tenured physics professor) level work or asymptotically approach web browsers without all that tedious attention to improvement and accessibility.

Qt pretty much nails this balance, WPF isn't bad either. Both will run circles around browsers at rendering performance and are much less tedious to develop in unless you've only done web dev before.

I have done both and I am not at all a fan of QT.

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

#676

Post by camgunz »

The answer to all this is: "use Qt".

"But camgunz, I only know JavaScript"

That's cool! Look into QML.

"But camgunz, I only know X"

That's cool too! Qt4 has a truly ludicrous number of language bindings: https://en.wikipedia.org/wiki/List_of_language_bindings_for_.... Qt5 has a fair number too: https://wiki.qt.io/Language_Bindings.

"But camgunz, I need an embedded browser"

I agree, separate windows are for savages. Qt has you covered with Qt WebBrowser.

"I need a native look and feel across all platforms"

Well, that's a pipe dream. BUT, you can get closer with Qt than anything else. Google for some screenshots.

"I need a bananas style but I don't want to write any code"

Qt supports CSS-like stylesheets!

---

The web isn't a good application platform. Sure we could (and have been) spend billions of engineering hours and years to get it up to speed with exactly what we have now, but that's obviously a bad idea. We can figure out zero-install and sandboxing, but we just don't need to shoehorn everything into JS, weird APIs like localstorage and webrtc, and the DOM. We just don't need to.

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

#677

Post by joelthelion »

bitwize wrote: post #469

An internet points out that Hackernews' favorite text editor takes up more CPU than the average Hackernews would have had at their disposal 20 years ago just to make the cursor blink on and off. Hackernews circles the wagons to justify the stupid engineering design decisions behind said editor based solely on the fact that embedding a complete Web browser just to draw buttons and text fields "won" over any sensible G…

I was with you until the non-sequitur about Wayland. What exactly is shitty about Wayland? It is way less bloated than X11.

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

#678

Post by mbel »

joelthelion wrote: post #677
bitwize wrote: post #469

An internet points out that Hackernews' favorite text editor takes up more CPU than the average Hackernews would have had at their disposal 20 years ago just to make the cursor blink on and off. Hackernews circles the wagons to justify the stupid engineering design decisions behind said editor based solely on the fact that embedding a complete Web browser just to draw buttons and text fields "won" over any sensible G…

I was with you until the non-sequitur about Wayland. What exactly is shitty about Wayland? It is way less bloated than X11.

The design of Wayland might be (and I believe is) superior to X11. Although as every piece of software on this planet in first years of its existence it will be incomplete, buggy and not compatible with all the other things that already exist. For some people this might be shitty compared to mature software, that is buggy but at least most of it's bugs are already known and worked around.

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

#679

Post by audidude »

fulafel wrote: post #656
tetromino_ wrote: post #554

Earlier quoted context omitted.

If by "responsive, fast, reliable" you mean awful screen tearing when you mix X11, OpenGL, and/or video playback. Fixing it on any given machine is often possible through some voodoo and a hand-rolled combination of driver and software settings, but that voodoo works only for one specific combination of hardware and driver version, and every update means more rounds of trial and error...

This is not because of X11 the protocol though, just implementation bugs. Thus not a good reason to start from scratch.

How would you suggest we fix the core pointer protocol? (It's not an extension)

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

#680

Post by dom0 »

symlinkk wrote: post #637
dom0 wrote: post #408

Earlier quoted context omitted.

Factually incorrect, since Qt uses native widgets when possible. Applying Qt stylesheets usually disables use of the operating system's styling engine, i.e. only then Qt starts drawing the widgets by itself. Widgets that are not part of the native widget assortment are drawn by Qt.

Then what is this blog post about? https://blog.qt.io/blog/2017/02/06/native-look-feel/

Qt Quick Controls which has nothing to with QtWidgets.

> Posted in Dev Loop, Qt Quick Controls, Styles

Post reply on HN