I imagine an IT technician running around pressing keys on real physical keyboards connected to all machines, instead of connecting via ssh, or even using Ansible.
Yeah this was what I was trying to get across to the other reply here. That tech is probably using VNC or something, rather than a shell over ssh. And they follow what I imagine are very bad docs from whoever built this thing, click on this, click on that, click loop video, click enable fullscreen.
And that was probably a requirement for the devs to deliver it that way. Because they know what kind of techs that customer hires to maintain these things. And anyone comfortable with Linux and the CLI is not applying for this technician job. (lol I’m making a lot of assumptions here. AITA?) This is the story I have created in my mind about this broken kiosk and I’m sticking to it.
I disagree. Using a DE is more ‘intuitive’, but using CLI commands I way easier and effective, if you know the commands. A couple of scripts can run on cron schedules and you can just forget about it until it breaks (if it ever breaks).
For a dev/engineer/linux user, I agree. For the IT technician who probably mostly works with Windows fixing printer drivers, who every now and then has to go change the ad content on the kiosks, he probably curses “that damn Linux” every time. I’m betting for him the CLI is not easier.
engineers are just letting
That’s a bold claim cotton, I’m sure there are no project managers, middle managers, or executives involved
Tbf it is a lot easier to just leave the DE running than try to tweak a non DE env, especially for media playing.
Also it is probably easier for whatever IT technician to use this thing, update content, do troubleshooting, etc.
I imagine an IT technician running around pressing keys on real physical keyboards connected to all machines, instead of connecting via ssh, or even using Ansible.
Yeah this was what I was trying to get across to the other reply here. That tech is probably using VNC or something, rather than a shell over ssh. And they follow what I imagine are very bad docs from whoever built this thing, click on this, click on that, click loop video, click enable fullscreen.
And that was probably a requirement for the devs to deliver it that way. Because they know what kind of techs that customer hires to maintain these things. And anyone comfortable with Linux and the CLI is not applying for this technician job. (lol I’m making a lot of assumptions here. AITA?) This is the story I have created in my mind about this broken kiosk and I’m sticking to it.
I disagree. Using a DE is more ‘intuitive’, but using CLI commands I way easier and effective, if you know the commands. A couple of scripts can run on cron schedules and you can just forget about it until it breaks (if it ever breaks).
For a dev/engineer/linux user, I agree. For the IT technician who probably mostly works with Windows fixing printer drivers, who every now and then has to go change the ad content on the kiosks, he probably curses “that damn Linux” every time. I’m betting for him the CLI is not easier.
As an engineer who actually made one of these systems, can confirm management drove the use of Ubuntu desktop