• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • tool@lemmy.worldtoProgrammer Humor@lemmy.mlC++ Moment
    link
    fedilink
    English
    arrow-up
    7
    ·
    4 months ago

    On Error Resume Next never before have more terrible words been spoken.

    Every time I’m reading a PowerShell script at work and see -ErrorAction SilentlyContinue I want to scream into a pillow and forcefully revert their commit.

    I’ve actually done it a few times, but I want to do it every time.






  • tool@lemmy.worldtoProgrammer Humor@programming.devWould you agree?
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    11 months ago

    If Linux was dominant it wouldn’t be Linux. There would be more pressure to monetize and there would always be someone willing to sell out for that money. You can see this even in the Linux community today. I’m sorry I had to be so negative about it though, it sounds nice.

    This is a very Desktop/workstation-centric view of the situation and you’re completely neglecting 3/4ths of the story. Linux is already hilariously dominant on the on-prem server and Cloud side of things. Like, it’s not even close. Pretty much any website you visit, the odds are overwhelming that it’s running Linux. Even Microsoft runs most of the underlying infrastructure for Azure and Github on Linux. Android is the #1 mobile phone platform in the world, which runs on, you guessed it, Linux.

    And it’s already monetized to the gills. Red Hat has multi-billion earnings per quarter, every quarter, and Canonical is almost certainly going to IPO this year.

    It’s already dominant in pretty much every space it touches and it has been for a very long time. Desktop/workstation is pretty much the singular exception to that.









  • tool@lemmy.worldtoProgrammer Humor@lemmy.mlIt's not great
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    On GitLab, you start from a docker image, so it’s harder to setup some things but easier for others. If you are very good at docker and don’t mind making your own images just for CI purposes, then go ahead.

    I think I’d probably consider myself at/near expert-level with Docker, but CI/CD runners instanced in containers just doesn’t work for some of our workloads.

    As an example, some of our projects have a bunch of Docker images that get built via their own Dockerfiles in the repo, are ran and discarded during the workflow, and each one is modifying the checked-out source tree in some fashion (NPM stuff, composer, whatever, etc), and then a final prod Docker image is built and tested from that source repo tree that has been modified by the Docker containers built/ran/discarded during the workflow. So in Gitlab, it sounds like we’d be running Docker in Docker for some projects.

    You ever ran Docker in Docker? It’s temperamental at the very best and there are a thousand gotchas associated with it, not to mention having to worry about how many variable scopes deep you are and keeping track of that, how to properly bind mount volumes into the nested Docker containers because the method and paths will vary depending on how nested you are, etc. It’s just an absolute nightmare to deal with all-around in that context.

    I’ll see if we have some projects I can try out on it, but the majority of ours are like what I described above.