Edit: 3 bytes, not 2 (thanks!)
Very annoying!
That kinda implies this isn't a small shop, so "breaking" a windows machine IT provisioned to put Linux onto it might be out of the question, both in terms of requisition, access to the UEFI, or even network configuration.
Or said coworker is more familiar with Mac/Windows than <Insert Linux Distro and particular window manager here>, so this is best of a bad situation.
You can domain join via Winbind or SSSD. Exchange via Evolution or Kmail and other work arounds exist. TPM 2.0 has been supported for quite a while so all good for encryption and other attestation tasks. We have rather a lot of host based firewalls (sore point 8) but it looks like the latest effort might stick for a while longer than the past ones.
...
Oh, you use that ... vendor ... SSL VPN. OK, can't do that and that's generally where it falls apart. We do have several.
I can and do operate solely on Linux but I have the benefit of owning the company. Some of my customers insist on their gear/setup for their environment and that's fine: they get to buy it too.
At a larger enterprise organization (that isn’t tech/FAANG) it could be considered a fireable offense.
Use it to make the world a better place.
From the original comment, it's likely an IT department, meaning a large org, meaning slow changing policies in place about how the machines are setup, often in order to meet even slower changed compliance laws.
Your seven different "vendors" solution to bodge domains/outlook wouldn't be supported by IT, which is a problem when then machine breaks or an audit happens...
It is, and it's even the default prompt in the Win+X menu
Is this still really a thing? even notepad can handle LF. I guess the default could still be crlf for some apps.
just change it to input and be happy
I see no other reason that maximum platform compatibility
I had had them setup with WSL as a way of moving forward, here's a few things I noticed:
- different home directories, the different distros are accessed as network shares. It can get confusing where "Home" is unless you explicitly stumble a few times and verify always where files are.
- Issues with CR/LF. You need to be careful using native windows tooling and having saved files in Windows line endings vs Unix. For non-savvy users the content looks correct but on Unix the tooling will fail in weird ways.
- Visual Studio Code integration was actually excellent, my coworker ended up using VS Code to do Filesystem operations more so than using Windows Explorer.
- The new Windows Terminal is fantastic, hopefully its bundled with Win 11.
I'm really grateful for the technical capabilities that WSL brings out. I hope the dev teams are focused on fixing the subtle UX issues that trip up users.