Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Windows is prohibited at Gitlab

about.gitlab.com

Post reply on HN
Print view View original

201–210 of 324 posts

Re: Microsoft Windows is prohibited at Gitlab

#201

Post by wkdneidbwf »

horsawlarway wrote: post #9

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…

developers using windows isn’t necessary to test web software on browsers on windows.

Re: Microsoft Windows is prohibited at Gitlab

#202

Post by 1970-01-01 »

habnds wrote: post #3

>> 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…

So they banned a wildly popular OS because it does not satisfy their security guidelines. I just checked, they have no guidelines for securing Windows. So you can't satisfy their Windows security guidelines because the guidelines for securing Windows were never written. What a joke.

Re: Microsoft Windows is prohibited at Gitlab

#203

Post by azangru »

rosmax_1337 wrote: post #196

I believe: 1) The reasons shown as to why Windows is prohibited are essentially parallel construction. 2) The real reason is because someone has an agenda against Windows and Microsoft. 3) This is quite alright. It might be a net loss in the short term for everyone, but a net win in the long term for everyone. Microsoft has a lot of bad stuff coming their way, for good reason.

> Microsoft has a lot of bad stuff coming their way, for good reason.

There are several good things that are currently coming out of microsoft:

    - vscode
    - typescript
    - github
    - npm
    - edge (at the moment, microsoft at least as strong supporter of PWAs as Google; and possibly even stronger)
Windows is probably not one of them.

Re: Microsoft Windows is prohibited at Gitlab

#204

Post by mobiuscog »

Halan wrote: post #39
mwint wrote: post #27

Earlier quoted context omitted.

I bought an M1 Max for the extra displays support, and the 64gb RAM support. Not that I need 64g, that was more because I found a decent deal on one that happened to be 64g. But I sure don’t complain about it :)

Good point for the extra displays but in this case they are using only 32gb which makes it a bit overkill unless they do video editing work

Or they use docker for mac

Re: Microsoft Windows is prohibited at Gitlab

#205

Post by Beltalowda »

sneak wrote: post #151
rlv-dan wrote: post #55

Earlier quoted context omitted.

As a long time Windows user, it would take me a considerable amount of time to get used to the operating system and all applications and utilities that I need to be productive. Not saying Windows is great, but it works for me. And I'm pretty sure they don't hire people to learn an operating system.

Another good feature of this policy is that it rules out people who explicitly identify themselves as "$OPERATING_SYSTEM user"s. Tying your identity (personal or professional) to some proprietary software brand is a little silly.

I'm a self-identified $OPERATING_SYSTEM user because I have been using $OPERATING_SYSTEM for 20 years in much the same way, like how it works, have a lot of things set up for it which is not always easily portable (e.g. scripts and programs I wrote), and have a lot of $OPERATING_SYSTEM things hard-wired in to my brain and muscle memory.

Can I spend time and effort changing that? Of course. But why fix something that isn't broken?

Am I tying my identify to $OPERATING_SYSTEM? No. It just works for me, so I'm a $OPERATING_SYSTEM user.

Re: Microsoft Windows is prohibited at Gitlab

#206

Post by [deleted] »

cwbrandsma wrote: post #186
politelemon wrote: post #54

> Due to Microsoft Windows' dominance in desktop operating systems, Windows is the platform most targetted by spyware, viruses, and ransomware. This is poor reasoning and a misunderstanding of how security works. Any org should be happy with any OS, as long as sufficient security controls for it exist. Anyone who oversees Windows estates, or works in desktop security, can tell you that they exist and are extensive, a…

Considering all the security software my corporation forces on all of us, each product hammering my CPU and RAM while I try to compile...windows is an issue for developer productivity. (I'm a windows based developer, I feel the pain)

[deleted]

Re: Microsoft Windows is prohibited at Gitlab

#207

Post by Beltalowda »

xeromal wrote: post #174
sneak wrote: post #151

Earlier quoted context omitted.

Another good feature of this policy is that it rules out people who explicitly identify themselves as "$OPERATING_SYSTEM user"s. Tying your identity (personal or professional) to some proprietary software brand is a little silly.

Yeah, we know exclusive Linux users are full of it.

I use Arch btw

Re: Microsoft Windows is prohibited at Gitlab

#208

Post by unixfg »

Xylakant wrote: post #57
eminence32 wrote: post #32

I wonder if this has anything to do with the fact that gitlab is fully remote. In an office where you have on-site IT staff, and a local corporate LAN, you can require every windows machine to be part of AD, have group security policies pushed out, and generally have tools available for central management. But with gitlab, everyone is working in their own networks around the world. That sounds like a very hard enviro…

Mobile device management is the topic. You can manage windows devices remotely, just as you can manage MacOS devices. No need for them to check in. It „just“ takes some effort, and if you have multiple operating systems to support, the effort is multiplied. But a company of their market cap and size probably should have the funds for a team dedicated to this.

BYOD certainly has its problems, but it doesn't seem like they're even trying.

"To provide proof of Full Disk Encryption, please do the following depending on the system you are running..."

Having your users send you a screenshot to verify device compliance is ridiculous.

Re: Microsoft Windows is prohibited at Gitlab

#210

Post by baal80spam »

Halan wrote: post #39
mwint wrote: post #27

Earlier quoted context omitted.

I bought an M1 Max for the extra displays support, and the 64gb RAM support. Not that I need 64g, that was more because I found a decent deal on one that happened to be 64g. But I sure don’t complain about it :)

Good point for the extra displays but in this case they are using only 32gb which makes it a bit overkill unless they do video editing work

Docker will eat this 32GB for breakfast.
Post reply on HN