Considering the base version of fvwm is no longer supported by anyone on planet Earth, it's there because it's deraad's preference, and that's fine.
Newer versions are available in ports.
It's important to remember that fvwm is customisable so it doesn't need to look dated. Given enough time, it's possible to have an environment which suits the individual just fine.
The lattice configuration comes from a conventional triangle mesh, so you can prepare it with any STL editor of your choice, and the lattice shape comes from a precalculated Fourier polynomial in barycentric coordinates.
There are many language features can be rewritten by hand into other simpler forms, you could rewrite loops into gotos, C++ objects into structures, etc. This does not show that those things are not useful. But the point of the article was not to show why nested functions are useful, for which I would certainly have used more interesting examples.
Location: Bogotá, Colombia
Remote: Yes
Willing to relocate: No
Technologies: HTML, CSS, JavaScript, TypeScript, SVG, TeX/ConTeXt, PHP, Jekyll, Tailwind CSS
Portfolio: https://miler.codeberg.page/
Résumé-CV: https://miler.codeberg.page/cv/cv-en.pdf
Email: Please see Portfolio or CV/Résumé
GitHub: https://github.com/acidrums4/
Experienced with both frontend and backend web development (PHP; Wordpress, Framer, some Joomla and some Typo3), iconography, editorial design/typesetting with ConTeXt, general graphic design and webmaster duties. Please feel free to check my portfolio for some examples of my work.
I think we agree on this. Fil-C does not ensure this. Showing the absence of run-time errors at compile-time is a hard problem, and the most realistic solution in general is via model checkers which I think would be the ideal solution, but we would need better tooling. Dependently types languages are also interesting.
In the context of existing tooling and C, there is also a lot of potential in using the optimizer to show safety properties. This works quite well to show the absence of signed overflow issues and null-pointer correctness, but still less well for bounds checking, e.g. see here for some preliminary experiments: https://uecker.codeberg.page/2026-05-22.html
In fact I employed the same idea for the slide stack site I use for teaching. Not exactly "URL is an app" but "URL is a slide"
https://okaleniuk.codeberg.page/blackboard/_1.html?sequence=...
The same consideration applies. No backend, no storage, also no user data collection, no authorization, no hurdles in general. Everyone can use it.