Live data from Hacker News

Microsoft Windows is prohibited at Gitlab

about.gitlab.com

251–260 of 324 posts

Re: Microsoft Windows is prohibited at Gitlab

#251

Earlier quoted context omitted.

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 didn't read it as cost, but management overhead. It's easily possible to secure a Windows computer in an enterprise environment. They are fully remote and primarily a Mac shop, so they don't have that expertise or infrastructure. If you are running Linux on a Dell, then they assume you have the ability to manage that yourself. I see this more as a function of them being fully remote more than anything else.

Then just say so instead of making excuses about security and cost. We also only buy a selected range of hardware and support a selected range of Operating Systems. But the reason is stated as “We currently don’t have the administrative capacity to support more than this. Period.” And that’s a fair reason and good reason and everyone understands that.

Re: Microsoft Windows is prohibited at Gitlab

#252
post #67

Earlier quoted context omitted.

I work there. (And have for the last 5 years.) Obviously I can't divulge anything confidential, but ask a more specific question and I'm happy to answer from my vantage.

What are the downsides of the culture?

- Transparency is amazing, but it doesn't always mean clarity. We try really hard to say "why not just what" but you won't always have or easily get all of the context because there is possibly a lot of context.

- Async is really hard for new folks to adopt to, and it can be hard for people to adopt to "you will be measured on your results, not hours worked."

- I think we've done a really decent job of navigating an organization with a huge amount of cultures represented, but adapting and then adopting a "company culture" on top of that can also be challenging for team members to understand. (Think some cultures are more direct, and others reserved). This doesn't play out in any kind of battle, just as a leader having to be extremely well-versed in a lot of global culture aspects.

Happy to answer other questions (again, within reason) if there are others!

Re: Microsoft Windows is prohibited at Gitlab

#253

Earlier quoted context omitted.

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…

> But why fix something that isn't broken? 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 base…

I like doing useful things; switching tools merely because a corporate policy says so is not useful (whether there are good or bad reasons for that policy is besides the point here).

Re: Microsoft Windows is prohibited at Gitlab

#254

Earlier quoted context omitted.

What if they're worried about the telemetry that would be going to their biggest direct competitor? Not a defense, just a curious thought.

Telemetry can be turned off. You can do it at org level, at department level, or individually. Use WPD, best tool for this.

To be clear, you're saying there is a way to prevent _any_ and _all_ data about the device and its usage ever being sent to MSFT? And it won't be overridden by Windows updates or any nonsense like that?

Re: Microsoft Windows is prohibited at Gitlab

#255
post #91

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…

For many years, and in so many companies, the policy has been the opposite. All company laptops must have windows, anything else needs to be vetted by the IT admin. Now that the Edge browser works fine on Linux, there's really no need for all these licenses, and someone needs to start to break the unhealthy dependency every company has on Active Directory.

Yep. I find it kind of surprising that this is news. There are so many companies where nothing but Windows is allowed, but not allowing Windows in one corporation with a major Microsoft-owned competitor is the issue?

Re: Microsoft Windows is prohibited at Gitlab

#257
post #93

Reading further on the page, the "Laptop Repair" part is interesting : >If your laptop is broken and needs to be repaired you can take it into an Apple repair store. You should ensure that you have a recent backup before doing so, and that your laptop is not your only registered device for iCloud two-factor authentication. >If the repair is not going to be too expensive (more than $1000 dollars USD), go ahead and rep…

And you need to have an appropriate Time Machine backup target...

Re: Microsoft Windows is prohibited at Gitlab

#258
post #71
post #46

Earlier quoted context omitted.

I do not believe those are sufficient for enterprise licenses, which must be provided separately.

There's no requirement to purchase an enterprise license. Large companies just do that to save money.

Wait, they buy a second license to save money? How does that work and, more importantly, how can I convince lots of folks to buy my product twice to save money?!

Re: Microsoft Windows is prohibited at Gitlab

#259
post #183

Earlier quoted context omitted.

Was your need to maintain KMS actually caused by a Microsoft requirement, or was it rather a cost saving and standarization measure?

It’s one of those “chicken egg” issues, ultimately it’s not enforced until certain scales. Microsoft does not like >200 machines being activated from 1 IP/Site for example. But you’ll run into issues running the “pro” version of windows, and you’ll need the enterprise version pretty early. Computers don’t ship with enterprise, if any do then it’s certainly not all of them. So you have to license all machines on your…

The more I read of Microsoft licensing, the more it feels like a scam.

Re: Microsoft Windows is prohibited at Gitlab

#260
post #78

I 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...

Even with WSL2?

Or you can just use the hardware the employer is paying for, plus paying you to use...
Post reply on HN