That is not necessarily a bad thing, sometime stability is what matters the most. But here the last commit was removal of a security and bugs branch...
Pug has been pretty complete for quite a while, there just isn't that big of a potential for insecurity for something that becomes vue's html/jsx at build time and 99% of run time threats is basically that the dev sent unsanitized use input to v-html instead of v-text.
The main problem with pug is that, AFAIK, vue is the only modern webframework with stable support for it.
It does, right? I imagine you would be map syntax highlighting rules and colour themes over to this convention in order to generate a new set of glyphs. I'm sure it isn't trivial but it could likely remove or at least alleviate one of the cons listed in the article.
This is one of the cooler things I've seen in a while!
Definitely! For example, Glyphs has a decent python scripting API which could be used to automate the whole process. I used it for automatically assigning each layer the correct color attribute to save me some clicks. And I also generated all the calt lookup rules from a list of keywords.
I wonder if you can load a font from base64 string like you can with images. Then, one may write a pure js library which generates such font from a set of rules on the fly. Catered to a specific use case.
I've had some form of personal site for more than 15 years now, usually with a hand-coded theme. It's unremarkable technically, but as a UX designer, it certainly gives me more confidence that I know how the web works.
How many lines does it take you to build a pixel buffer in WebGL? SDL2 here is being used to handle input, open a window, and update a texture stretched over the full window using a software-rendered buffer of pixel data.
Probably about the same. Most of the code is defining data types and loading an OBJ file, and modern OpenGL requires quite a lot of boilerplate before anything gets drawn.