this post was submitted on 20 Nov 2023
998 points (93.4% liked)
linuxmemes
21197 readers
106 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
My company is currently working through this.
The entire dev team has Macs. Most have Intels. Many are on M1. Some are on M2.
Security/IT teams feel the pain, dealing with all sorts of weird things. And their solution lately is saying "fuck it" and giving the dev a M2. Which is a bandaid as what if M3 and onwards continues to break something?
Fortunately, my team builds software and runs everything through docker.
It's not like this came out of the blue. The PowerPC to Intel transition was recent enough that it's still fully documented on the web with forum posts by frustrated users. It's Apple. Their attitude has always been that users have to deal with it.
And yet they have a reputation for being easy to use.
That's Apple brainwashing. Anyone who ever tried to offer remote support via TeamViewer probably knows how Mac users then fail to grant screen recording and input permissions to TeamViewer. Before they do that on their own, they can get any remote support.
I do the same. Docker buildx to the rescue.