• 0 Posts
  • 385 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle


  • Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

    If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

    there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

    Again, by experience, this is assuming a lot.




  • folkrav@lemmy.catoLinux@lemmy.mlOptimize your shell experience
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    17 days ago

    I do connect to VMs and containers all the time, I just don’t see a reason not to speed myself up on my own machines because of it. To me, the downside of typing an alias on a machine that doesn’t have it once in a while, is much less than having to type everything out or searching my shell history for longer commands every single time. My shell configs are in a dotfiles repo I can clone to new personal/work machines easily, and I have an alias to rsync some key parts to VMs if needed. Containers, I just always assume I don’t have access to anything but builtins. I guess if you don’t do the majority of your work on a local shell, it may indeed not be worth it.


  • folkrav@lemmy.catoLinux@lemmy.mlOptimize your shell experience
    link
    fedilink
    arrow-up
    19
    arrow-down
    3
    ·
    edit-2
    17 days ago

    I’d rather optimize for the 99% case, which is me getting shit done on my machine, than refuse to use convenient stuff for the sake of maybe not forgetting a command I can perfectly just look up if I do legitimately happen to forget about it. If I’m on a remote, I already don’t have access to all my usual software anyway, what’s a couple more aliases? To me this sounds like purposefully deciding to slow yourself down cutting paper with a knife all the time cause you may not have access to scissors when you happen to sit at someone else’s desk.








  • As of 2021, the US spent 16.6% of its gross GDP ($23.59 billions) on healthcare expenditures. The very next was Germany, at 12.7% of its $4.28 billion GDP. The US is spending more per-capita than any other OECD country on healthcare, it’s just not made visible by looking at the number on your tax report. You’re still collectively paying for it one way or another.

    But hey, yay, low taxes. Good for you, I guess?


  • Considering how little we actually know, how much we are still figuring out today, how wrong we once were, and most definitely still are on many things, about said nature, the naturalistic argument is IMHO rather weak. The argument silently assumes too many things, at least with our current knowledge - that human beings do actually have an inherent nature, that said nature is uniform enough across the whole species to make that generalization, that said nature is inevitable and can’t be evolved past or rationalized against, that it always was the case and will always be, etc.




  • I’m not sure if you’re agreeing or trying to disprove my previous comment - IMHO, we are saying the exact same thing. As long as those stranded travelers or data breaches cost less than the missed business from not getting the product out in the first place, from a purely financial point of view, it makes no sense to withhold the product’s release.

    Let’s be real here, most developers are not working on airport ticketing systems or handling millions of users’ private data, and the cost of those systems failing isn’t nearly as dramatic. Those rigid procedures civil engineers have to follow come from somewhere, and it’s usually not from any individual engineer’s good will, but from regulations and procedures written from the blood of previous failures. If companies really had to feel the cost of data breaches, I’d be willing to wager we’d suddenly see a lot more traction over good development practices.