Arghblarg

-credit to nedroid for strange art

  • 67 Posts
  • 661 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle



  • Good for Mint. Someone has to keep app and lib developers honest, not hiding behind packaging every app with its special-snowflake version of every dependency. (And I’m a developer, so I know it isn’t always easy to make an app robust against upstream version changes, but ignoring the reasons something might break can cause one to overlook possible errors or invalid assumptions in one’s own code.)

    Tools to aid in mass-deployment are nice, but they shouldn’t be a crutch to hide overly-sensitive apps from their host OS’s valid version changes and updates. IMHO.












  • Aren’t you at all curious why it failed though? (If not, no harm no foul – I certainly know time diagnosing a bug is always in short supply, from personal experience). What if it’s a symptom of something important that might happen later even in Fedora 41?

    Sometimes it just feels like containers are used as justification for devs to blow off bug reports. As a dev I want to understand why a failure occurs.


  • Agreed there – it’s good for onboarding devs and ensuring consistent build environment.

    Once an app is ‘stable’ within a docker env, great – but running it outside of a container will inevitably reveal lots of subtle issues that might be worth fixing (assumptions become evident when one’s app encounters a different toolchain version, stdlib, or other libraries/APIs…). In this age of rapid development and deployment, perhaps most shops don’t care about that since containers enable one to ignore such things for a long time, if not forever…

    But like I said, I know my viewpoint is a losing battle. I just wish it wasn’t used so much as a shortcut to deployment where good documentation of dependencies, configuration and testing in varied environments would be my preference.

    And yes, I run a bare-metal ‘pet’ server so I deal with configuration that might otherwise be glossed over by containerized apps. Guess I’m just crazy but I like dealing with app config at one layer (host OS) rather than spread around within multiple containers.



  • ArghblargtoProgrammer Humor@programming.devWorks on my machine
    link
    fedilink
    arrow-up
    132
    arrow-down
    45
    ·
    8 days ago

    Call me crusty, old-fart, unwilling to embrace change… but docker has always felt like a cop-out to me as a dev. Figure out what breaks and fix it so your app is more robust, stop being lazy.

    I pretty much refuse to install any app which only ships as a docker install.

    No need to reply to this, you don’t have to agree and I know the battle has been already lost. I don’t care. Hmmph.