Tuesday 244

WordPress Co-Founder Matt Mullenweg Is Not a Fan of JAMstack – The New Stack

Filed under: Computers, Open source — zundel @ pm

Matt Mullenweg, founding developer of WordPress and CEO of Automattic, thinks the currently trendy JAMstack approach to website management — which decouples the frontend from the backend, and doesn’t require web servers — is a backward step for the web. “JAMstack is a regression for the vast majority of the people adopting it,” Mullenweg told…

Source: WordPress Co-Founder Matt Mullenweg Is Not a Fan of JAMstack – The New Stack

Saturday 52

Discord Is Not An Acceptable Choice For Free Software Projects

Filed under: Open source — zundel @ pm


Thursday 29

Move Fast and Fix Things – The GitHub Blog

Filed under: Computers — zundel @ am

Efficiency is fundamental in these kind of projects because even with the performance improvements they entail, it becomes hard to justify the time investment if we cannot wrap up the refactoring in a tight timeframe.

Without a clear deadline and a well defined workflow, it’s easy to waste weeks of work rewriting code that will end up being buggier and less reliable than the old implementation.

One of the old insights of big iron programming.
Making the code better could so easily cost more in breakage, and then fixing that, than improving the code could possibly save.

The lifetime of the code almost always got underestimated, easy to see in hindsight. But the math asked for the expected life of the code, how much could the improvement be expected to save, versus the cost to develop then debug it.

A lot of big iron programming, like this core GitHub function, had zero, really zero, tolerance of fault.

Source: Move Fast and Fix Things – The GitHub Blog

Monday 26

Org-Mode Is One of the Most Reasonable Markup Languages to Use for Text

Filed under: Computers — zundel @ pm

Org-Mode Is One of the Most Reasonable Markup Languages to Use for Text

Source: Org-Mode Is One of the Most Reasonable Markup Languages to Use for Text

Wednesday 0

Xfce Brightness Key Fine Control Solution

Filed under: Open source — Tags: , — zundel @ am


The keyboard provides too coarse control of brightness.
In low light the roughly ten steps of keyboard brightness control provide too coarse control at the dim end going from too dim to too bright in one step.


Power Manager Plugin

Power Manager Plugin provides a slider to control brightness.

If you see a battery icon in the panel, click or right click on it to get a brightness slider.

There seem two Panel battery icons available. The one provided by Power Manager has fewer options and needs a right click to get to the brightness slider.

To add the Power Manager Plugin,
right click on an empty area of the Panel
(default Gallium OS configuration has the panel along the bottom of the screen)

Panel menu item
Add New Items… sub menu item\

Select the Power Manager Plugin
Add button

Click on the new battery icon to access the brightness slider.
Scrolling on the slider still provides only coarse control. Clicking provides finer control but still not good at low levels.

If you now have two battery icons in the panel, Xfce Power Manager has also displayed an icon.
Go to Settings menu, Power Manager, General tab, and set "System tray icon" off.


sudo apt install brightnessctl (if you do not understand this, do not use it)
(brightnessctl also of course available via App Grid or Synaptic)

Brightnessctl has a nice wealth of commands and options.
man brightnessctl also brightnessctl -h

Test brightnessctl in the terminal to find the settings you like.
I use brightnessctl s +4% and brightnessctl s 4%-

Then bind a brightnessctl command to a key.
Got to Settings, then Keyboard and the Applications Shortcuts tab.
Click the Add button.

I bind to the brightness control keys with Shift key. There’s a *nix pattern of using the Shift key for a modified command. (Shift+XF86MonBrightnessUp and Shift+XF86MonBrightnessDown)

(brightnessctl may fail for you depending on the permissions you have set for your user account.)


apt search is your friend.
apt search brightness

It annoyed me. It’s *nix: I get to fix it.

Lots written on the web about this. Not liking what I saw written. Thus this post.

xbacklight fails and not worth the xorg.conf fuss to make it work.
Also not going to patch xfce4-power-manager. Etc: all more work and less robust.

And as always -> Arch!

This will come in Xfce, just not yet.


Monday 363

Filed under: Open source — zundel @ pm

Sunday 362

Vim’s Big Idea – Mike Kozlowski – Medium

Filed under: Computers — zundel @ pm

Learning the lesson of vi

Source: Vim’s Big Idea – Mike Kozlowski – Medium

Monday 300

Asynchronous Communication: What It Is & Why You Should Care About It

Filed under: Computers — zundel @ pm

Doist CEO Amir Salifhefendic explains what asynchronous communication looks like in practice and how to create a more async culture at your company.

Source: Asynchronous Communication: What It Is & Why You Should Care About It

Sunday 285

The end of uBlock Origin for Google Chrome? – gHacks Tech News

Filed under: Computers — zundel @ pm

Source: The end of uBlock Origin for Google Chrome? – gHacks Tech News

Monday 32

Dyslexia font

Filed under: Computers, Open source — Tags: , — zundel @ pm

A fiend brings to my attention news of a font to help with dyslexia: Dyslexie.

I forget not everyone lives in open source.

See OpenDyslexic:

We most easily read proportional text with serifs: quickly and smoothly — and go right past error.s We best edit mono-spaced text.


Mono-spaced text also works well for dyslexia.
A mono-spaced font with slab serifs may work especially well.

I do almost all reading and editing in dark green mono-spaced text on a soft yellow background (“#003300 #FFFFCC“), reducing glare and eye strain, and assisting acute vision spotting errors.

Saturday 30

Off to Idaho

Filed under: Computers, Open source — Tags: — zundel @ pm

Fin by Keith Wesolowski

Want a ranch hand?

Meanwhile the most trumpeted “advance” of the last 10 years at the bottom of the stack is UEFI, which replaces parts of the system firmware… with a slightly modernised version of MS-DOS. It’s painfully obvious that the sole purpose of UEFI is to enable Microsoft to continue collecting royalties on every computer sold, a brilliant move on their part given the steady decline of Windows, but an abomination for everyone else. UEFI solves no problems for the operator, customer, or OS vendor. If anything, it creates more of them. There’s a better way to do this, but my central observation is that the solutions that would be better for everyone else are not those that would be best for the vendors: AMI, Microsoft, and Intel are quite happy with their cozy little proprietary royalty machine and have no incentive to engineer, or even enable others to engineer, anything better. The bottom of the stack is designed to serve vendors, not customers.

The net result of all this is that we have data centres occupying many hectares, filled with computers that are architecturally identical to a Packard Bell 486 desktop running MS-DOS long enough to boot a crippled and amateurish clone of Unix circa 1987…


I became a bicycle mechanic (by accident).
Not nicer people.
Not nicer businesses.
But more pleasant problems.

We, computer tech, have great tools. I love using them.
But the problems became old, repetitive, and uninteresting decades ago.
Didn’t matter if I developed or customized accounting software or recovered another server hosed by a rank amateur with all thumbs. Old uninteresting problems.

Bicycles have old repeated mistakes (stuff known a hundred years ago). I try to avoid those. But the day to day problems, what needs fixed, I enjoy.

Friday 29

How it’s done

Filed under: Computers, Open source — Tags: — zundel @ am

Making it Virtually Easy to Deploy on Day One by John Goulah

Oh hell yes.

Some people just set it up better than others.

Older Posts »

Create a free website or blog at WordPress.com.