A 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.
Microsoft Windows is prohibited at Gitlab
311–320 of 324 posts
Re: Microsoft Windows is prohibited at Gitlab
#312Earlier quoted context omitted.
What are you looking for? Managing Linux at scale is extremely easy as you can leverage basically all the tooling that sysadmins use(d) for management of infrastructure fleets. You can even get a pretty GUI if it’s saltstack enterprise.
Something like saltstack is not in the same league as point and drool windows solutions.
Arguably learning the idiosyncracies of proprietary management tools is harder long-term as there are myriads of edge cases and they get replaced with completely new tools quite often.
Exceptions are SCCM maybe, but people are avoiding that as much as possible IME.
Re: Microsoft Windows is prohibited at Gitlab
#313Earlier quoted context omitted.
Something like saltstack is not in the same league as point and drool windows solutions.
Is there something you can’t do? Or are you assuming sysadmins don’t learn their tools. Arguably learning the idiosyncracies of proprietary management tools is harder long-term as there are myriads of edge cases and they get replaced with completely new tools quite often. Exceptions are SCCM maybe, but people are avoiding that as much as possible IME.
I'm sure you could achieve similar results with Salt but it will be some bespoke contraption requiring a lot of engineering effort where you cant just hire new staff off the street to maintain it.
Re: Microsoft Windows is prohibited at Gitlab
#314Earlier quoted context omitted.
Is there something you can’t do? Or are you assuming sysadmins don’t learn their tools. Arguably learning the idiosyncracies of proprietary management tools is harder long-term as there are myriads of edge cases and they get replaced with completely new tools quite often. Exceptions are SCCM maybe, but people are avoiding that as much as possible IME.
Most Windows compliance tools are seen as a tick in a box so ease of use and low effort deployment is often the most important thing. I'm sure you could achieve similar results with Salt but it will be some bespoke contraption requiring a lot of engineering effort where you cant just hire new staff off the street to maintain it.
I’m sure certain things are a tick of a box, with salt it’s usually 3-5 lines of yaml. It’s not like you’re writing a management system by hand in a general purpose programming language.
Re: Microsoft Windows is prohibited at Gitlab
#315Earlier quoted context omitted.
Most Windows compliance tools are seen as a tick in a box so ease of use and low effort deployment is often the most important thing. I'm sure you could achieve similar results with Salt but it will be some bespoke contraption requiring a lot of engineering effort where you cant just hire new staff off the street to maintain it.
Tell me what you need and I’ll tell you how hard it is. I’m sure certain things are a tick of a box, with salt it’s usually 3-5 lines of yaml. It’s not like you’re writing a management system by hand in a general purpose programming language.
Re: Microsoft Windows is prohibited at Gitlab
#316Earlier quoted context omitted.
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
#317Earlier quoted context omitted.
So, you think a very small Modul that communicates via http only, and written in different language then the main project (go instead of Ruby), is a reason that the developers of the main project (ruby, only supported on Linux) should also be able to work on Windows, or even be supported in doing so, cause ~three people need to support the gitlab-ci runner on windows? Edit: oh, and testing of those gitlab-ci function…
Since when CI/CD products like a compiler, static analysis, os frameworks are a very small module? If they aren't running Windows, I really doubt their skillset to give any kind of meaningful support.
Re: Microsoft Windows is prohibited at Gitlab
#318I guess Gitlab doesn't care about having customers that work on Windows platforms. Meanwhile Github works just great for us.
100% Agreed. The really aggressive "fuck Microsoft" rhetoric is going to burn a lot of these startups over the long haul. It's incredible to me the number that still seem to be operating in an ideological bubble that was originally created 2 decades ago. A lot of Serious Business happens on top of Microsoft technology right now, and the companies responsible for tending to solutions in this space are made extraordina…
Re: Microsoft Windows is prohibited at Gitlab
#319Earlier quoted context omitted.
Since when CI/CD products like a compiler, static analysis, os frameworks are a very small module? If they aren't running Windows, I really doubt their skillset to give any kind of meaningful support.
Since when does Gitlab(-CI) Provide a Compiler or OS Framework? Gitlab-CI allows you to execute commands in some form of defined environment (Container based, insite a VM or on bare-metal), They have to make sure the commands are executed in the order you defined, and the output is then shown in the WebUI. Everthing run is "random" cli-tool you "found" somewhere.
Re: Microsoft Windows is prohibited at Gitlab
#320Earlier quoted context omitted.
Since when does Gitlab(-CI) Provide a Compiler or OS Framework? Gitlab-CI allows you to execute commands in some form of defined environment (Container based, insite a VM or on bare-metal), They have to make sure the commands are executed in the order you defined, and the output is then shown in the WebUI. Everthing run is "random" cli-tool you "found" somewhere.
I thought they wanted to compete against GitHub offerings, apparently not.