Earlier quoted context omitted.
Most places I've worked at (Windows shops largely) had management tools that worked well on Windows but not as well on other devices. The IT staff was skilled largely in Windows, as well. The biggest argument against other OS options was that we simply did not have the tools and experience to effectively manage the other options. It's a valid argument, and seemed disingenuous to take digs at the other OS options when…
Microsoft Windows with AzureAd and Intune provides a suite of tools for managing your fleet of laptops at little to no additional cost. It's honestly so much for free that running any other suite of laptops becomes arduous and expensive. It all just works out of the box and it's easy to bolt things on. The viruses and malware argument is ludicrous if you do any amount of end point protection. Apple is a walled garden…
Microsoft Windows is prohibited at Gitlab
221–230 of 324 posts
Re: Microsoft Windows is prohibited at Gitlab
#222This is not actually that unusual; in fact, if I'm not misremembering, Google also does not generally allow Windows, aside from some limited, less privileged stuff.
Re: Microsoft Windows is prohibited at Gitlab
#223>> 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…
I‘m a bit surprised that they care about the cost so much - the Dell laptops and the Apple Laptops come in at a price point of 2000 - 3000 USD and the Dell they specifically recommend for Linux use comes with Windows Pro preinstalled. The price difference to the equivalent Linux version is around 70USD. That‘s a negligible difference, especially when you start comparing to the employees wage (It‘s probably about 1 ho…
I see this more as a function of them being fully remote more than anything else.
Re: Microsoft Windows is prohibited at Gitlab
#224Earlier quoted context omitted.
I don't get it, is the complain about the "you can ensure your teams are working at the right things at the right time" part? How is wanting your products to be aligned with their vision evidence of dysfunction?
It implies a major problem in their org is/was pesky developers working on things that weren't assigned. Why weren't those things assigned? Bad PMs who don't care about the pain developers feel? Not enough developer freedom? The fact that the roadmap is completely disconnected from what's actually important for the business/developers? It's a product for developers; the developers should know better than anyone what…
I've seen developers work on just completely the wrong stuff, and their entire salaries was 100% pissed away, or in some cases, even more than 100% because they added net-negative value.
You really need to optimize hiring the right people with the right mindset and have a good team lead/manager which balances developer autonomy with business interest. I have thus far not seen it work outside of fairly small teams, although I agree that in principle it's the best way to make a good product and keep your developers happy.
Re: Microsoft Windows is prohibited at Gitlab
#225>> 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…
> Due to Microsoft Windows' dominance in desktop operating systems, Windows is the platform most targetted by spyware, viruses, and ransomware. That may be true, but a much higher proportion of downloaded Mac software lacks code signing. Opting in to that as a developer on the Mac will carry a lot of risk of kafkaesque deactivation and, and most don’t want to deal with that. On Windows, on the other hand, it’s like g…
Citation? I can't recall the last time I ran across a Mac app that wasn't signed - most are Notarized.
Re: Microsoft Windows is prohibited at Gitlab
#226I mean, they use Rails, and Ruby/Rails are annoying to use on Windows. I imagine Windows is a massive headache not worth dealing with considering their stack...
Re: Microsoft Windows is prohibited at Gitlab
#227I mean, they use Rails, and Ruby/Rails are annoying to use on Windows. I imagine Windows is a massive headache not worth dealing with considering their stack...
Re: Microsoft Windows is prohibited at Gitlab
#228I'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…
instead, invest in:
- real automated testing (to the extent technically and economically feasible). One hack is to get customers and partners to fund it, then leverage outsourcing.
- feedback from users - make it easy, streamline responses, setup escalation. Understand that you can't nail down everything and quickly triage issues. Scale the team so at least you can do the triage.
Re: Microsoft Windows is prohibited at Gitlab
#229Earlier 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.
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…
Because this can be a form of brokenness. Someone would be hired for their aptitude and probably not because of something they have already repeated over and over (unless we include factory work). The ability to adapt and create (and be creative) is usually not described as such in SWE work, but a lot of the actual work does include that.
That said, if a job has a match based on OS, it would probably just as much be a good thing to explicitly know that you either will be or won't be a good fit based on what you are used to and what you think you can adapt to. Knowing this about a job or a potential hire saves everyone a lot of time.
Re: Microsoft Windows is prohibited at Gitlab
#230A company forbidding the use of Windows (and more broadly Microsoft products/services) would be a huge green flag to me. I don't even care why. I would miss VS Code though.