Microsoft Windows is prohibited at Gitlab
about.gitlab.com
Microsoft Windows is prohibited at Gitlab
1–10 of 324 posts
Re: Microsoft Windows is prohibited at Gitlab
#2I think it's risky because a small computing monoculture can feel complete but commit a software business to failure at the very beginning by rejecting 90% of the potential market.
Re: Microsoft Windows is prohibited at Gitlab
#3 Due to Microsoft Windows' dominance in desktop operating systems, Windows is the platform most targetted by spyware, viruses, and ransomware.
macOS is preinstalled on Apple computers and Linux is available free of charge. To approve the use of Windows, GitLab would have to purchase Windows Professional licenses, as Windows Home Edition does not satisfy GitLab's security guidelines.
As many purchases of laptops have occurred with employees making the purchases and then being reimbursed by GitLab, a remote employee would typically be making a purchase of a laptop pre-loaded with Windows Home Edition.
Windows Home Edition is notoriously hard to secure.
edit: after thinking about this for a bit, it occurs to me that their main competitor is github and that maybe they just aren't very excited to use MSFT products?Re: Microsoft Windows is prohibited at Gitlab
#4Re: Microsoft Windows is prohibited at Gitlab
#5Re: Microsoft Windows is prohibited at Gitlab
#6It's a fairly odd that that IT cultures are segregated into places that have nothing but Macs and other places that have nothing but Windows. I think it's risky because a small computing monoculture can feel complete but commit a software business to failure at the very beginning by rejecting 90% of the potential market.
Re: Microsoft Windows is prohibited at Gitlab
#7Re: Microsoft Windows is prohibited at Gitlab
#8I really wonder what it's like inside Gitlab. The product ticks all the boxes you'd want it to, but the user experience just resonates with sadness and misery.
Re: Microsoft Windows is prohibited at Gitlab
#9If nothing else - what's not used is not tested. And if you expect any real population of users to be using Windows machines with your products, you should have developers/PMs/QA/support interacting with your products using Windows machines.
I see this as: We're saving a bit of money and making ITs life easier, and in exchange users will get a worse product.
Realistically - that's a bad trade. It is almost never the right decision to prioritize IT quality of life over basically any other business need.