YAML here as well.
Configuration many levels deep gets so much harder for me to read and write in JSON with all [], {} and ""
Also the lack of comments... And YAML still is more used in software I'm using than JSON5, so I'd rather skip yet another format/library to keep track of.
You are completely right about SwitchOS, and it is even more exciting that some models sells in two versions, with the only difference being called CSS* for SwitchOS, or CRS* for RouterOS. And the SwitchOS-enabled model is much cheaper, so customers ordering for themselves almost always pick the wrong one (that is, SwitchOS, which we can't manage properly in our automations and other software solutions).
My collegues wouldn't appreciate my shell config in the root account, especially the vi bindings ;)
As long as /bin/sh isn't pointing to zsh, you haven't messed anything up. A lot of public scripts wouldn't expect to be run under zsh.
If you write your own scripts, I'd say to use zsh, but start it with #/bin/zsh (or whatever resolves to zsh) to be explicit about the fact that it is designed for zsh and nothing else. Most scripts written aren't going to be distributed to hundred of thousands of systems, but at most used in a handful of systems. No point in not enjoying some things zsh does better in scripts.
A lot of systems have other dependencies as well, and as long as a system which has scripts in it is specifing zsh along with other dependencies, I wouldn't see the problem. zsh doesn't take up much space or introduce other problems just by being installed.
As for the root shell, you can put Defaults env_keep += HOME in your sudo configuration. That will have sudo -s run your usual zsh with its usual configuration for interactive, daily use. Be aware of any config that shouldn't be run as root.
sudo -i will still run the shell root is assigned in /etc/passwd, and everything run as root would function ar expected.
Can only agree on Mikrotik routers. All are using RouterOS, which works the same on all their devices, from routers to switches and access points.
They are relatively cheap for the capabilites you're getting. They have their own scripting language, two APIs (their new one is REST-based).
GUI (winbox is recommended, and plays nice with wine. Wouldn't recommend web interface, just cumbersome) and CLI exists.
They have a lot of builtin functionality, like DHCP server, DNS server with static configuration, and even file sharing. Some models are powerful enough to run Docker images on (yes, that's builtin...).
We're running a couple of hundred and don't have much problem with them.
We're using Ansible for a lot of stuff, with Semaphore as a frontend.
Semaphore has rudimentary support for CI/CD. We don't need all the bells and whistles of something like Jenkins, and Semaphore is saving us from having yet another software to know and and maintain.
st from suckless all the way. Used it a couple of years now in conjunction with i3. I'm spawning a lot of terminals, doing a few commands and closing them often, so starting quick is a must.
Wrote a small patch that allows me to copy current directory from a terminal instance to primary selection with a keybinding. That allows me to quickly navigate to whatever directory that would be in another terminal or application.
I guess that means able to access services on the Internet over IPv6, not me being able to get a /64 and providing services myself to others.
Sort of ok for phones I guess, although not as great if someone doesn't have access to fiber and have to use a mobile link in a residential environment.
Bahnhof actually just provides NAT:ed fiber connections as well as default, but will issue a public, unique IP if asked (at no additional cost).
I liked the look of Dashy, but it felt somewhat too heavy software for the simple dashboard I needed, and so I wrote the first version of Dashie.
It only uses Javascript and doesn't need any server components except a webserver. Configuration is done by editing YAML files.
Themes are implemented, and multiple pages which can be used to make more complex navigation of multiple dashboards.
Check it out :)
In Sweden we have just one ISP for non-commercial customers providing native IPv6 adresses (Bahnhof) on fiber connections, and even then we can't get a static prefix from them.
Not quite sure on the mobile ISPs though.
Somewhere along the lines of 10-15 years?