More and more arch based non-systemd projects are converging to Artix, officially or unofficially we can’t tell, as officially Arch-OpenRC and Manjaro-OpenRC have taken the responsibility for the Artix creation.
Arch-Bang has switched its repositories to artix and was updated last August 17 2017. But switching repositories alone does not automatically make a distribution an artix. Yet again, as with Manjaro, there seem to be slight structural differences and configurations.It comes with a very plain autologin of openbox on its live installer. The installer is simple with step by step q/a and works as a terminal-graphic/tui. You better not jump any steps or it will backfire on you.
There were some glitches to fight with on networking (it comes with adequate firmware), and localization peculiarities. It is still a pain trying to get a second language keyboard and back, but once I figure it out I will post the exact method. Trying to use lxpanel instead of tint2 so I could have an easy keyboard switch locked the whole system. After some investigating and search it appears that much of the LXDE related packages have come from Debian based systems un-audited. I didn’t have any problems with the same from arch/artix.
(update 10 hours later): All I wanted was to add functionality for a 2nd language keyboard, it took hours and countless reboots to see the effects. I nearly had a stroke, but ended up with gxkb on tint2. Not the simplicity of having alt-shift as I always had, now I have to click something in the midst of typing something on a window, but I gave up. Nearly gave up on this arch-bang because of this as I’ve never had this problem before. Never got lxpanel to work either. I did follow instructions for doing exactly what I wanted to do from Arch and Manjaro wikis. Not only did they not accomplish the task, for a while one of the modifications that seemed pretty standard on Arch broke the X-server which refused to start. Something about keyboard definitions in /etc/X11/xorg.conf.d/20-keyboard.conf which the X on arch-bang can not accept. Just removing or commenting out the conf releases the X). Feel free to contribute any alternative solutions.
What I ended up with was a very lean in RAM openbox, no usual display manager, it starts openbox from X, autologins the user and gives the user no prompt for password sudo rights. Great for a VM or a fully encrypted installation. Anywhere on the menu (or obmenu) that you may be used to having gksudo to run something as root, on this setup you can use sudo and it starts up. A good but dangerous thing if you are not conscious of doing just that.