• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 2nd, 2023

help-circle


  • I think it is safe to say that OP’s question was lay speak for “what is the mean time to get to a result”. Other than that I don’t think you actually addressed the question.

    Let me try to get it started:

    Randomly generating music might be akin to password cracking. Cracking short or simple passwords can be very fast, while cracking long or complex passwords can be very long. The rate of password guessing also affects the time to get a result.

    To calculate an answer, we need the following information:

    • Guessing speed (how fast is each “song” generated and checked?)
    • Minimum “song” length that needs to be generated
    • Complexity of “song”: how many instruments (“voices”), resolution (are whole notes only ok, or do we need. Half or quarter notes?)
    • Settle on some subjective definition of “song”. Is S.O.S. in morse code a “song”

    You might be able to take a genre of music, and decompose the songs within to get some answers… I don’t have the time for that. Anyone want to take a stab at estimating the calculation?





  • SkyNTP@lemmy.mltoSelfhosted@lemmy.worldDocker is hard work
    link
    fedilink
    English
    arrow-up
    3
    ·
    19 days ago

    I guess it depends what you run, and how the projects/containers are configured to handle updates and “breaking changes” in particular.

    But also, I’m being a bit broad with the term “breaking changes”. Other kinds of “breaking changes” that aren’t strictly crashing the software, but that still cause work include projects that demand a manual database migration before being operational, a config change, or just a UI change that will confuse a user.

    The point is, a lot of projects demand user attention which completely eclipses the effort required to execute a docker update.