I understand the motive to let readers get up and running quick, getting some graphical window instead of terminal black box, but if you think users want to avo

I understand the motive to let readers get up and running quick, getting some graphical window instead of terminal black box, but if you think users want to avoid terminals and get to graphics, why spend a chunk of the article talking about it? Just when readers starting to like the terminal and the culture, the author goes "anyway, terminal sucks, let's get a graphic window! here's 100 lines of code you'll never understand" I don't understand the bloat of introdocing gtk, meson and ninja, more deps means more code, more code means more bugs, more steps and more difficult to compile, I'm sure a lot of people will fail to compile this, which is very frustration for beginners who're not familiar with error messages. You might think meson and ninja makes it easy for building, but that's wrong, that might be true for engineers who build 1000 times a day, not for one off beginner situations like this. Abstractions is for people who understand why the abstraction is needed.