Well they haven’t seen much abuse yet. They just dodged a nice bump in inflation for a month.

On a side note, wasn’t this the guy that Sean O’Brien praised for being pro-worker?

Shit must be bad.

How’re Chinese GPU/AI chip designs coming along?

Probably.

Last year, the teams responsible for Pixel hardware and Android software were merged into one division, and Google today announced a “voluntary exit program” for employees working in the Platforms & Devices group.

At least there’s some plausible reasoning for this, instead of blanket headcount reduction to pad profits. Reasoning doesn’t change much of course.

but doesn’t DeepSeek’s ability to harness less lower quality processors thereby allow companies like NVIDIA and OPENAI to reconfigure expanding their infrastructure’s abilities to push even further faster?

Not that much if the problem is NP-hard and they were already hitting against the asymptote.

Increase your monthly donation to Wikipedia.

Or Saudis?

If they can deliver. But hey, we’re the VCs now. Not everything succeeds.

Are eggs gonna get cheaper now?

Also: what the actual fuck.

They’re probably showing up on this chart. They should keep going.

Source: https://pubs.acs.org/doi/10.1021/acs.estlett.4c00907

A shutdown would be preferable than a sale of the active app and userbase to Elon no?

Yes

Among other things:

• anti workers rights
• anti immigrant
  • with exceptions for his own businesses
• anti safety nets
• pro fascist
  • he’s began propping up Reform in UK and AfD in Germany
• pro corporate

Basically your bog-standard right-wing corporate fascist grab bag. He’s using his platforms (in all meaning of the word) to push that internationally.

Check the first comment on this turd nugget from last week: https://x.com/RealAlexJones/status/1877066245192794146

My first instinct was to poke fun but it’s actually important to keep breaking this overpaid influencer’s false image. He’s actively using it to push his harmful agenda.

Still sounds like it could get quite messy if Google adds a feature

Of course it can, the point is how difficult it is to get out of the mess. Patching upstream source directly is magnitudes worse. Unfortunately, when you want to add one button to SystemUI somewhere, going straight to the layout and adding it in is most tempting.

In practice, an upstream merge would typically be completed in a few days to several weeks at worst with little to no breakage. These days that’s even easier because a lot of pieces got modularised and separated as part of the work done in Project Treble.

It depends on the problem, language, framework and what the options are. If at all possible, write stuff without touching upstream code. If you’re working in a modular, pluggable system, there’s a lot you can do this way. In Android specifically, you can do a lot by writing components that plug into the Intent framework. When it comes to modifying upstream code, you use whatever facilities the programming language offers to minimize the lines of code changes. Ideally only modify upstream code by adding a single line in a module. E.g. write a separate Java module, import it into the upstream code and call it in a single new line in the appropriate block. Then do your work in your module, import and call additional things as needed. Surround the added line with consistent labels in comments. Enforce this in code review and ideally automation. When a code drop comes, git can often automerge such additions. When it can’t, the merge tools make it very clear where your changes are as they aren’t intermixed all over the upstream code, making the merge work easier. There were some clever tricks with branching that I don’t recall. You could even write your own tooling to help with any of this. There’s clever things you can do with the build systems too. None of this is too complicated that a competent software team can’t figure out if given the direction and time to do it.

“We’re under attack from the front left and front right. Respond accordingly”

slow-clap

There’s also difference in how much work the maintenance of forks is depending on how they implement new features. There are many ways and the easiest ones are typically the least maintainable. Designing those features in order to minimize maintenance work when new code drops from upstream can dramatically change the equation and therefore the fork viability. I’ve worked at an Android mobile OEM and dealt with code drops from Google and Qualcomm. Every OEM essentially maintains a fork of Android and deals with a massive set of changes with every Android release. Implementing stuff by straight modifying Android source files lead to huge maintenance workload. After going through a few code drop cycles we devised a set of strategies that drastically decreased the effort needed.