Mail-in-a-box FTW.
l3mming
joined 1 year ago
Brilliant. Now you just need to mix the audio with a little animated paperclip.
"probably won’t be very good content for the average human to view"
Well, no changes there then.
Have a look at the pygame library for python. It's a great first step for this kind of thing. It has everything he needs to grasp the concepts and start to build some cool stuff. Then move to Godot.
Forget window managers and definitly avoid Electron if you can. Easiest way:
firefox --kiosk https://your-app-url
I have to resolve them way more than I should. We have internal devs and external devs and there is a lot of treading on toes. For any conflict that isn't super obvious (90% are) ^*^ I just ask the two devs involved to resolve it together, in a sensible way that keeps the unit tests working.
^*^ Usually the non-obvious conflicts are the ones where it's not just a matter of choosing A or B, but splicing A code with B code.
Your principal architect sounds like an idiot.
But how will they have time to learn SELinux and run a business?
If Snowden can exfiltrate data from the NSA, there is simply no way for your average employer to prevent this through computer restrictions. Effort in that direction is a total waste of money.
This is a company policy issue, enforced through non-disclosure agreements and, ultimately, the legal system.
Agreed. I manage both of these transparently beyond the employee's view. All the employee knows is that they have xyz free space to use on their profile.
Would this locked-down distro be used by customers or by employees? If it is being used by employees, there is no faster way to be hated than putting unnecessary restrictions on their logins. You don't want that kind of workplace.
I simply do this:
-
Make sure they don't get sudo/root privileges.
-
Remote mount their home directories (nfs).
-
Don't add any restrictions beyond that. It is a waste of time and money.
-
Control the rest through company policy, usually clauses under the 'Misuse of company network' section.
-
Who cares if employees are browsing tik-tok or whatever if they've done all their work? That's a work-allocation issue. If they haven't done all their work then that's already a solved problem. Either motivate them or performance manage them slowly towards the door.
-
Who cares if they want to install xyz software [in their home directory]? Chances are it'll be a free boost for performance and/or morale.
Well, no, and that's the whole problem; Systemd removed choice, and it was designed to do so. That is why there is so much anger. It is bad software design, by design. It flies in the face of the core linux principles, all in the name of homogenising the linux ecosystem, and you know exactly which big corporations benefit from that.
The simple fact is: today, if I want to run a mainstream distro without Systemd, I cannot. Its cancerous tentacles run so deep that decoupling it from a mainstream distro, and keeping it decoupled, is a full time job.
Instead I have no choice but to run a smaller, less featured, less secure and less funded alternative.
Full credit to Devuan, MxLinux, Artix, and the other united underdogs.
Fuck you Redhat/IBM and your proxy evil-doer Lennart.