I love this idea. It's not meant to teach people everything, but it shows the basic SELinux concepts in a fun manner, that is different from the typical dry written documentation.
The best utility that this has is that it gets people asking questions. I could put this on my wall at work, and then when my colleagues ask about it, I could use it to segue into actually teaching them about SELinux. Putting the SELinux text documentation on my wall would not have the same effect.
Can you describe your workload and your experience with InfluxDB? We evaluated InfluxDB in 2015 and found that it fell apart due to the large amount of data we produce. I'd be interested in hearing your experiences to see if we need to reevaluate.
Workload is mostly writing incoming metrics from many dynamic instances (AWS). In 2015 Influx was at pre-1.0 and definitely had a tendency to "fall apart" under stress - for one, there were no memory limitations implemented, so an accidental large query would eat up all your memory and kill the database. To be fair, no one recommended putting it in production at that point. It's just that I needed something to run a Graphite-like metrics platform at scale and it had to be future-proof. Bit of a gamble but it turned out well! :)
This is an interesting external approach to metaprogramming in Go. After working with languages that have full metaprogramming capabilities, you really take for granted what metaprogramming gives you. The section "The Problem" really drives it home for me.
I hate to be that guy, but Slackware has been around for longer than FreeBSD, it beats it by a few months. One of Slackware's goals is to be Unix-like, and that decision is definitely evident in the distribution.
Thanks for pointing that out! Post updated. Slackware was first distro I ever used seriously, after getting hooked up on Linux with a Red Hat 5.0 or 5.1 CD that was attached to a (printed) IT monthly newspaper. I have to tell, FreeBSD feels kind of similar to Slackware.
The best utility that this has is that it gets people asking questions. I could put this on my wall at work, and then when my colleagues ask about it, I could use it to segue into actually teaching them about SELinux. Putting the SELinux text documentation on my wall would not have the same effect.