Hi!

First, the big subject of this article series is *web applications* and not *web pages*. It's a bit confusing because any web application is also a web page. Let's make it clear.

Web page:

https://www.bobsprite.com

Web app (for computer only):

https://www.bobsprite.com/editor

The web page is constructed in plain HTML and works fine.

The web app I had to rewrite, porting a lot of HTML elements to my JavaScript/canvas elements. It was a lot of trouble? Yes. But it was necessary and I am very happy with the result (although there is room for some improvement).

---

Second, about web pages, I just think that there are some cases where using an image (file or canvas) guarantees the expected result everywhere. I didn't say to not use HTML and CSS. I think the title of the article is affecting people too much.

---

Now, replying your items:

About accessibility:

BobSprite is a drawing tool. It must preserve its layout to work properly. It is not a drawing tool for people with some eye disease. Maybe one day I will create a special version for them; canvas based, of course.

About "If Chrome is doubling your menu, there's something wrong with how you coded the menu.":

Can't Chrome be bugged? How can you be so sure that it was my fault? You never read the code or even visited the site. So much faith in Google...

About "HTML and CSS are piss simple.":

I respect your opinion, but I think don't think so.

About "If you're having these types of problems it means you are learning from the wrong sources, and failing to embrace how they are supposed to be used.":

Possibly. But I have studied in (apparently) serious books. I will welcome any source reference that you may share.

About "It's also quite telling... frameworks...":

I am not sure what you mean. I can say that I don't rely on any framework. I write all my code on pretty simple text editors.

About 'Seriously, your "this text fits well" and the form after it reek of having mixed metrics. PX is not your friend, stop using it. Fixed widths are not your friend, stop designing for it. Fixed layout is broken garbage, STOP IT!

That "this text fits here" issue for example implies you fixed the width of the container, fixed its height, and/or turned off wrapping. That is NOT how ANY of this stuff is supposed to be used!':

This is the point of the article: getting real control of the web application. It's for the situations where we don't want the browser to decide the layout.

Finally, I am not alone:

October 3, 2017 Daniel Imms, @Tyriar

The rendering engine of the Integrated Terminal has been completely re-written with performance in mind for the upcoming version 1.17 of Visual Studio Code. In this version, we move away from a DOM-based rendering system to using the HTML canvas element.

https://code.visualstudio.com/blogs/2017/10/03/terminal-renderer