I'm no fan of Windows myself, but I find this a fairly bad policy. If 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 p…
I mean, Gitlab is a web platform. It's pretty easy to test how it's going to work on different platforms without needing full machines. Heck, you can even just get Microsoft Edge binaries on macOS and Linux if you want to test Edge. But failing that, VMs are pretty sufficient.
Microsoft Windows is prohibited at Gitlab
41–50 of 324 posts
Re: Microsoft Windows is prohibited at Gitlab
#42I guess Gitlab doesn't care about having customers that work on Windows platforms. Meanwhile Github works just great for us.
It's just their workforce, where they don't want to see anyone working with windows.
Re: Microsoft Windows is prohibited at Gitlab
#43This is being posted just a day after this tweet: https://twitter.com/allenholub/status/1555324387087097856 I 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.
"GitLab plans to automatically delete projects if they've been inactive for a year and are owned by users of its free tier."
Which I hadn't heard. That's.... something.
Re: Microsoft Windows is prohibited at Gitlab
#44Whatever works. There isn’t some sort of diversity and inclusion requirement for OSs
Re: Microsoft Windows is prohibited at Gitlab
#45I'm no fan of Windows myself, but I find this a fairly bad policy. If 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 p…
Why? Gitlab is not a Windows application per se. Either you use a browser or git on the cli.
Git for windows is also notoriously different when it comes to edge cases, so in Gitlabs place I‘d be absolutely happy to have developers that use that OS as a daily driver.
Re: Microsoft Windows is prohibited at Gitlab
#46Earlier quoted context omitted.
Although not even hinted at in the doc, I personally find the tedium of buying and provisioning and monitoring licenses worse than the cost of it. I suppose you are also inviting risk in the form of an audit.
Most windows laptops today come with a license key baked into the BIOS. So no need to manage licenses here.
Re: Microsoft Windows is prohibited at Gitlab
#47Consider linux dominance on end-users devices through android and embedded systems like smart tv's. There are more instances of linux running and being used right now by end-users than windows. UNIX legacy and a long maturation process on HPC and servers probably has to do with how linux systems evolved to be so secure today compared to windows; also because of "bad-habits" windows historically brings.
It may sound cheesy and although I'd like to see linux more used on the desktop, I'm pretty happy with the current situation.
Re: Microsoft Windows is prohibited at Gitlab
#48>> GitLab approves the use of Linux, and Apple's macOS. Microsoft Windows is prohibited for the following reasons: 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 l…
A buy something with windows pro is not hard to communicate...
Re: Microsoft Windows is prohibited at Gitlab
#49How do they develop and test the gitlab runner for Windows then?
Re: Microsoft Windows is prohibited at Gitlab
#50I'm no fan of Windows myself, but I find this a fairly bad policy. If 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 p…