Perz1val 10 days ago

Yeah and everybody was complaining how slow the builds are for years. I really want to know too

pastage 10 days ago

I would much rather they spent that on having the devs network and travel, the servers work.

  • melodyogonna 10 days ago

    Why are the builds failing then?

    • tcfhgj 10 days ago

      planned obsolescence by Google

      • shadowgovt 10 days ago

        Beginning to use a CPU opcode that is 19 years old doesn't feel like planned obsolescence. if anything, it feels like unplanned obsolescence... "Oh hell what do you mean your CPU doesn't have that opcode no we've just been running the compiler with the default flags and that opcode got added to the default two months ago after a 10-year fight about the possible consequences of changing defaults!"

        Although I'm a little surprised to learn that the binary itself doesn't have enough information in its header to be able to declare that it needs SSSE3 to be executed; that feels like something that should be statically-analyzed-and-cached to avoid a lot of debugging headaches.

lupusreal 10 days ago

Probably a case of "don't fix it if it ain't broke" keeping old machines in service too long, so now they broke.

  • FirmwareBurner 10 days ago

    That's like ignoring your 'Check Engine' light because the engine still runs.