Madhur Ahuja madhur

INTRO

Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".

Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).

Let's dig in:

Goroutines

Think twice before abandoning Xorg. Wayland breaks everything!

Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.

Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.

As 2024 is winding down:

	-- awesomewm fancy_taglist: a taglist that contains a tasklist for each tag.

	-- Usage:
	-- 1. Save as "fancy_taglist.lua" in ~/.config/awesome
	-- 2. Add a fancy_taglist for every screen:
	-- awful.screen.connect_for_each_screen(function(s)
	-- ...
	-- local fancy_taglist = require("fancy_taglist")
	-- s.mytaglist = fancy_taglist.new({
	-- screen = s,