Not OC question, but rather copied this from the pragmatic programmer

As a user, would you rather (1) wait for them [the software dev/company] to get all the bugs out, (2) have complex software and accept some bugs, or (3) opt for simpler software with fewer defects?

  • IWW4@lemmy.zip
    link
    fedilink
    arrow-up
    2
    ·
    2 days ago

    I have been fiddling and much later working in IT since 1985 and i have never seen finished software.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 days ago

    Love Unix principle: do one thing and do it right.

    So I look for quite stable and simple software rather than huge over complex monsters that are never really finished or ready (yes IBM and Microsoft I look at you)

      • Shimitar@downonthestreet.eu
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago

        I like and use gimp (well… Kind of moved to Krita but still use gimp sometimes) but of course are you referring to the unfinished state or the complexity?

        Gimp does one thing only, i don’t recall it can act as a code editor or a browser or a file manager etc etc … It is a complex thing it does, but the problem underlying it tries to solve is complex.

        Over-complexity is related to the complexity of the problem to solve, not to the complexity of the tool that you use.

        So a simple solution to a complex problem is also a complex solution in itself…

  • Hawke@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    In general:

    • I would rather not wait. This mostly benefits everyone: user gets to see what is coming, developer gets feedback, and depending on software maybe user can start getting the benefits sooner
    • on the other hand, it has some risks: maybe devs spend time fixing problems instead of bigger “building the system” tasks. Maybe users get attached to the “pre-release way of doing things” even if the final release is better. (Early access game mods can be very vulnerable to this)

    Complete vs simple software, it depends on what the job is. Some complexity is fine, and some bugs are fine, as long as there is a plan to get to where you want the software to be.

  • solidheron@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    That’s kinda complicated. I thought about underdeveloped interface but a perfectly working backend.

    If it functions but like the interface is difficult than pressing button

  • Zahtu@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    if it does not fit my purpose (aka software is unfinished), i will not use it and will not wait for bugfixes. so either (2) or (3)