AI ‘Bloat’ in browser blowing up CPU and drains battery

Slashdot tells us that a new “AI-bloat feature” of Firefox 141 blows up CPU and energy usage referring a neowin.net article that luckily offers an easy solution: disabling it. Here’s how:

you can disable them through the browser’s advanced settings. Head to about:config in a new tab, accept the risk warning, and use the search bar to find the controls. To kill the AI chatbot feature, search for browser.ml.chat.enabled and set it to false. To stop smart tab grouping, search for browser.tabs.groups.smart.enabled and set it to false.

Stop GNOME Software Background

To avoid GNOME Software from running in the background, you can take several approaches based on the solutions discussed in the context.

One effective method is to disable the autostart entry for GNOME Software. This can be done by copying the file /etc/xdg/autostart/gnome-software-service.desktop to ~/.config/autostart and adding X-GNOME-Autostart-enabled=false at the end of the file. This prevents the process from starting upon boot, which can free up significant memory.

Additionally, you can turn off background downloads by using the command gsettings set org.gnome.software download-updates false. This setting can also be adjusted through the preferences GUI of GNOME Software.

If you prefer a more direct approach, you can use terminal commands to stop the GNOME Software process. Run ps -el | grep gnome-software to check if it is running, and then use the command killall gnome-software to stop it.

Another method involves disabling the GNOME Software service by removing the autostart file located at /etc/xdg/autostart/gnome-software-service.desktop.

Lastly, you can configure your network connection to “metered” which might help in preventing GNOME Software from running in the background.

By implementing these methods, you can effectively prevent GNOME Software from running in the background and reduce its impact on system resources.

Farewell, spacevim, welcome lazyvim

Today I wanted to add dart support to my spacevim setup, so I opened https://spacevim.org/. What a surprise, I got redirected to https://wsdjeg.net/why-spacevim-is-archived/ that stated

SpaceVim 这一项目起源于 2016 年 12 月份,于 2025 年 2 月 21 日停止维护。

Thanks to Firefox automatic translation I read that

The SpaceVim project originated in December 2016 and was discontinued on February 21, 2025.

Needless to say I was a little mithered. Luckily there are several other “(neo)vim distribition” that turn our beloved editor into a full-fledged IDE. Since I have been told by my fellows of PoUL that even LunarVim is not so healthy I followed their suggestion installing lazyvim.org which is NeoVim-specific but worked out-of-the-box. Well, almost. In fact its dart support require a fairly recent version of NeoVim (0.10+) and I discovered after a while that I was running a not so current release (0.9). After adding flutter/dart support following this Reddit comment, it worked like a breeeze.

Continue reading

The fastest USB

The fastest USB key are not normal memory sticks but SD cards of a decent class with an USB-C 3.1 adapter

This is the suggestion from Davide Depau, found running several benchmarks with EtchDroid

SD cards are made to put them in cameras and it’s not uncommon to get 300 MB/s write even with a phone.

The slower ones do 100 MB/s on average

Whereas I haven’t found a way to get consistently fast USB sticks. The more expensive ones are generally better but not always. On average, flash drives do not do more than 70 MB/s and after a while they drop even slower when they run out of cache. So do SD cards, but they generally have bigger caches and hardly fill it up with the ISO of arch

Also, in the last 10 years I have noticed (empirically) a substantial improvement in the durability of SD cards. 10 years ago half of even branded SD cards would die on me, now even the ones from the fucking sub-brand on Amazon are OK