• Potatos_are_not_friends@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    1 year ago

    Eli5 answer:

    Typically, when devs build a product, a common method is to gather backend devs, frontend devs, ux designers, devops, project managers, etc. Everyone meets periodically and explains status and bottlenecks.

    In open-source, you don’t have that. It’s whoever is willing. Extremely rare are meetings. Often discussion happen in issues, PR, or somewhere else.

    In typical development, backend devs work on something and get feedback from frontend devs, who get feedback from ux designers, all up the chain.

    In open-source, backend devs try to create interfaces that anybody can tap into. They think about all the use cases, and create ways for someone else (ux and frontend) to tap into. Thats also separation of concerns, as backend handles business logic and frontend handles user interaction.

    If a backend dev does a good job, then the flexibility allows the User interface to shine. That’s what we’re seeing here.