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

Re:VS Code uses 13% CPU when idle due to blinking cursor ren... by pjmlp on Thursday March 23, 2017 @02:38PM (#13942735)

That is not true, before DirectX there was WinG and there were quite a few good games done in WinG.

The lack of games was mostly due to reluctance of game developers to abandon Assembly and using directly PC hardware, specially because C and C++ compilers were "too slow".

[ Parent | on HN ]

Re:VS Code uses 13% CPU when idle due to blinking cursor ren... by kayamon on Thursday March 23, 2017 @05:10PM (#13944319)

WinG didn't come around until 1994 though. If you wanted to ship a game in 1990, you had a choice of using GDI or using MS-DOS.

And the "assembly" argument doesn't make any sense. You can program Windows games in assembly if you want.

[ Parent | on HN ]

Re:VS Code uses 13% CPU when idle due to blinking cursor ren... by pjmlp on Thursday March 23, 2017 @07:20PM (#13945252)

Windows only became relevant for home users after version 3.0, actually the 3.1, which was released in 1992, so of course no one was shipping Windows games in 1990!

Sure you can use Assembly on Windows and there were a few books teaching exactly that, but you weren't allowed to touch the graphics hardware any more, unless you were doing a graphics driver, and do all those graphic card tricks, specially mode X.

[ Parent | on HN ]