I dont think Google is gimping your device to sell you new ones.
What you probably see is Google toggling on some new AI feature, which is now doing some initial on-device computation. It will usually calm down after a few days.
> I dont think Google is gimping your device to sell you new ones.
I'm not sure.
Last year they ruined my Pixel 4a by pushing that battery patch to everyone (even to end of life devices).
Their official repair center replaced the battery as per Google's guidelines and offer but during the battery swap they managed to physically break other parts of the phone over the course of multiple visits. Each visit broke a new component.
Google support didn't do anything in the end, eventually ignoring me. This went on for almost 6 months with an email chain over 100+ replies.
Eventually the repair center gave me enough credit towards a new phone (this 9a) but only after I mentioned I was going to small claims court since they left me with a device that didn't function in the way it used to function before I visited them.
There are tons of evidence showing that cameras are alone are not safe enough and even Tesla has realized that removing lidar to save cost was a mistake.
In raw power x64 is still the king, has always been.
You can skew things by looking only at single core performance (where apples most expensive cpus might win because of their strategy of having fewer but more powerful cores + memory latency gains are much more visible with only one core).
With that said, things are changing in the PC landscape and some extremely powerful and power efficient ARM designs are coming soon. We have already seen a small glimpse of that with MediaTek.
I just looked into that for this thread, but the highest-end Apple chips (M4 Max/M5) outperform the fastest normal Ryzens in both single core and multi core tests.
They're awful for gaming, which most benchmarks online are run for, but it takes a Threadripper to dethrone Apple's impressive CPU performance.
Of course, this also has to do with their integrated memory architecture, which isn't very popular with high-end PC customers who like the ability to upgrade their RAM.
It is hard to compare apples to oranges, sometimes people benchmark different software (e.g. Safari on osx vs Edge on windows) or software that on one platform is more optimised. But in general it looks like AMD despite using an older process node is doing fairly good.
What I need is an emacs with more lisp and less javascript.
If you want a really lean emacs-like editor, there is always mg and microemacs.
Edit: not trying to be a dick or a gatekeeper. This is HN, all ideas should be welcome including the one that dont make sense to some people. And always interesting to see contributions from Japan.
To answer the "Why Electron and JS?" question from the thread: honestly, it didn't start as a strict technical decision. It started purely out of my curiosity as a software engineer.
I use VS Code at work, and I just wanted to see what its underlying technology (Electron) was like to build with. Once I started playing with it, I realized it was a remarkably solid and flexible platform. That inspired me to try building something I had always wanted: a zero-setup, lightweight Emacs-like editor.
As a happy side-effect, using web technologies allowed me to use the Japanese IME without any stress, just like Windows Notepad. Unlike Windows Emacs, which sometimes requires special configurations, I was able to make it work just by running elecxzy.exe.
So while it lacks the beautiful Lisp ecosystem of true Emacs (like Lem), it started as a fun technical exploration that eventually became my daily driver!
> What I need is an emacs with more lisp and less javascript
Lem[0] in ncurses mode might be your friend. Unfortunately the BDFL deprecated the SDL frontend seemingly due to the SDL3 breakages, but the web one uses webview + a homegrown system instead of electron and framework magic, so it's still fairly lightweight
its main proposition is that the whole thing is written in Common Lisp, so it retains the hackable model of traditional Emacses without retaining the legacy of GNU Emacs
What you probably see is Google toggling on some new AI feature, which is now doing some initial on-device computation. It will usually calm down after a few days.