mkalygin

This is such a comprehensive analysis, thank you. For someone just starting to learn about the field, it’s a great way to understand what’s going on in the industry.

AFAIK Paper.js doesn't support WebGL and uses canvas. WebGL also applies anti-aliasing, which may be a reason of blurring.

I'm not familiar with PixiJS in any way other than knowing that it's a game engine. What is the difference between doing single PIXI.Graphics for the whole canvas vs PIXI.Graphics for every rectangle? Pros / cons?

FWIW the code in the post doesn't use sprites. I think it is done intentionally because not all of the engines support sprites. As someone mentioned in this thread if PixiJS would use sprites, it could be 10x faster.

Interesting. On my iOS device and on MBP PixiJS is the fastest. Any idea why PixiJS can be slower on Android devices?

I totally agree with you. In most of the cases this is the most reasonable strategy, unless you really understand what you do. A lot of good code bases live this way. There are usually too many things contributed to existing code. A complete rewrite worth it only when you know for sure, that you can throw away most of the details and nuances of the existing code.

I know that. I mean that I love HN mostly for smart comments. Sometimes I don't read an article, I read its comments. :) But blaming without evidence is not that kind of comments.

I can see that people on HN blame other countries easily without any real evidence...

I also noticed that simple questions somehow get higher popularity. If you ask something very specific to your problem, chances are this question won't be answered and also will be downvoted. So people rather answer "how to find an object in JS array" rather than "I have this weird error in X library, how to fix it?". But in my opinion, basic stuff is not what you face with in everyday job. It's all these unexpected errors, bugs and lack of documentation, what makes you Google it. In this sense, GitHub Issues does a better job than SO.