>they have $80k in their coffers but I am curious why they haven't spent $2-3k on one of those Zen4 or Zen5 matx consumer Epyc servers

I would also like to know this.

▲

pastage 3 days ago | parent | next [-]

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

▲

melodyogonna 3 days ago | parent | next [-]

Why are the builds failing then?

▲

tcfhgj 2 days ago | parent [-]

planned obsolescence by Google

▲

shadowgovt 2 days ago | parent [-]

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.

▲

tcfhgj 2 days ago | parent [-]

> "Oh hell what do you mean your CPU doesn't have that opcode [...]"

hobbyst dev? sure

Google? nope

	▲	shadowgovt 2 days ago \| parent [-]
		Did they make any explicit guarantees that their newly-cut binaries would continue to support 20-year-old architectures? Googlers aren't gods. It's a 100,000-person company; they're as vulnerable to "We didn't really think of that one way or the other" as anyone else. ETA: It's actually not even Google code that changed (directly); Gradle apparently began requiring SSSE3 (https://gitlab.com/fdroid/admin/-/issues/593#note_2681207153) and Google's toolchain just consumed the new constraint from its upstream. Here, I'm not surprised at all; Google is not the kind of firm that keeps a test-lab of older hardware for every application they ship, so (particularly for their dev tooling) "It worked on my machine" is probably ship-worthy. I bet they don't even have an explicit architecture target for the Android build toolchain beyond the company's default (which is generally "The two most recent versions" of whatever we're talking about).

▲

Angius 2 days ago | parent | prev [-]

They clearly don't

▲

lupusreal 3 days ago | parent | prev | next [-]

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 2 days ago \| parent [-]
		That's like ignoring your 'Check Engine' light because the engine still runs.

▲

Perz1val 3 days ago | parent | prev [-]

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