• originalucifer@moist.catsweat.com
    link
    fedilink
    arrow-up
    83
    arrow-down
    2
    ·
    edit-2
    11 months ago

    this prolly wasnt a bad decision early on… why push something to a population who cant utilize it… but shit changes fast, google.

      • originalucifer@moist.catsweat.com
        link
        fedilink
        arrow-up
        9
        arrow-down
        2
        ·
        11 months ago

        was it ignorance or malicious intent?

        if it was a person, i would try and assume ignorance… im not sure google the company deserves such respect

        • villainy@lemmy.world
          link
          fedilink
          English
          arrow-up
          11
          ·
          11 months ago

          Or it’s a company so fuckoff huge that one department (Chrome on Android) couldn’t get a bug report escalated in another department (YouTube). Eventually they just put in a UA workaround while the bug rots in a backlog somewhere. Common enterprise bullshit.

          Or the Chrome on Android team didn’t even bother reporting the issue to YouTube and just threw in a cheap workaround. Also common enterprise bullshit.

          • lolcatnip@reddthat.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            11 months ago

            Bingo. When I was a Chrome developer working on video stuff, we mostly treated YouTube like a separate company. Getting our stuff to work with theirs was a priority, but no more than, say, Netflix. We pretty much treated them as a black box that consumed the same API we provided for everyone.

      • ericswpark@lemmy.ml
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        11 months ago

        Could be that the developers for the HiSense TV just copy-pasted whatever UA into their browser codebase and called it a day.