Sciter Notes application has been published

September 10, 2017

Filed under: Design,Sciter,Web Application Techologies — Andrew @ 4:41 pm domain and project is for sale

August 22, 2017

Filed under: HTMLayout — Andrew @ 2:29 pm domain and project itself is for sale.

If you are interested please drop me a message.

New in antivirus protection: smart cable

April 29, 2017

Filed under: Curiouses — Andrew @ 10:53 am

The cable is not smart enough to remove viruses but as they say it can suppress some noise effects of them, at least.

Ah those smart marketing people …

Epic discussion: VS Code Uses 13% CPU When Idle Due to Blinking Cursor Rendering

March 24, 2017

Filed under: Design,Web Application Techologies — Andrew @ 9:57 am

VS Code Uses 13% CPU When Idle Due to Blinking Cursor Rendering

Discussions: Reddit and Hacker News

Couple of citations:

Assuming 1 million users of VS Code This blinking cursor will waste $3 million per year in electricity costs, and output 32,000 tons of c02 per year.

2150: “Grandpa, why did the ocean’s dry up?”
“well sonny, long ago, Microsoft didn’t optimize their code for a code editor’s cursor and pushed earth’s climate over the edge”


All this is about Microsoft Visual Code editor that is Electron application — Chromium based.

They blink cursor by this CSS declaration:

@keyframes monaco-cursor-blink {
    50% {
        opacity: 0;
    100% {
        opacity: 1;

.cursor-blink {
    animation: monaco-cursor-blink 1s step-start 0s infinite;

Problems with this solution:

  • In chromium / webkit this animation runs with animation frame rate — each 16ms — 60 FPS.
  • As Chromium (WebKit with Skia backend) uses mostly CPU rasterization than simple task of filling 1px rectangle eats CPU (and so drains batteries). On each frame rate whole window gets updated.

In principle all this can be solved by something simple as:

setTimer(function() { caret.toggleClass("visible") }, 1000);

When you want to ask for help in programming …

October 17, 2016

Filed under: How-to,Philosophy — Andrew @ 11:54 am

then use the following template:

  • Explain details that you see as much as possible. Environment, problem, etc.
  • Explain exactly what you want – what you think should be happening.
  • Explain what is actually happening.
  • Explain why you think it should be working differently.

By walking through all these steps you may find answer by yourself. In any case this will greatly increase a chance of getting adequate answer fast.

“Expert’s pyramid”

October 10, 2016

Filed under: Philosophy,Web Application Techologies — Andrew @ 11:15 am

Does front end developer need to know anything except of __HIS_FAVORITE_FRAMEWORK_HERE__ ?

From Dmitri’s Pavlutin “The path of software development craftsmanship”

Next Page »